Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 113234
interpreted = N
texte = 822 Hi Christophe This thread has been idle for a while now but I do think it is relevant = to revive it again. Have you had any thoughts about getting the original functionality = behind [ipaddress] to work as intended after the introduction of macOS = Sierra. I have made some investigation my self and I have not found any = easy (if any at all) solution to get the clients IP address using the = [ipaddress] function nor have I found any easy (if any) way to safely = disable the reverse proxy. I would naturally appreciate if the tag worked again since it is the = prerequisite to much code, other functions like [Session], etc. = regardless of who made the actual change, WebNDA or Apple... I am looking forward to you reply and am in need :) /Palle > On 5 Jul 2016, at 13.02, Palle Bo Nielsen
= wrote: >=20 > Hi Stuart >=20 > Thank you and I appreciate your example, which I understand. >=20 > /Palle >=20 >=20 >=20 >> On 04 Jul 2016, at 01:36, Stuart Tremain wrote: >>=20 >> After having worked with WebDNA on windows and now Linux in a number = of different hosting environments I have found different things = happening with [IPADDRESS] >>=20 >> Lately using Amazon with a load balancer I found that I needed to = look at the headers being sent back from the load balancer, in there I = found that the visitors IP address was being sent in a custom header = while [IPADDRESS] only returned the ipaddress of the load balancer. >>=20 >> Maybe if you are doing something a bit differently such as Palle is = you may find that you will have to write a custom function. >>=20 >> [TEXT]VIPADDRESS=3D[LISTMIMEHEADERS = name=3DX-Forwarded-For][VALUE][/LISTMIMEHEADERS][/TEXT] >>=20 >> It changed again when I then used their CDN =E2=80=9CCloud Front=E2=80=9D= , this is my solution: >>=20 >> [IF ("[ListMIMEHeaders = name=3DUser-Agent][value][/ListMIMEHeaders]"=3D"Amazon CloudFront")][!] >> [/!][THEN][TEXT]VIPADDRESS=3D[GREP = search=3D([^0-9\.])&replace=3D][MIDDLE = StartAfter=3D&EndBefore=3D,][LISTMIMEHEADERS = name=3DX-Forwarded-For][VALUE][/LISTMIMEHEADERS][/MIDDLE][/GREP][/TEXT][/T= HEN][!] >> [/!][ELSE][TEXT]VIPADDRESS=3D[LISTMIMEHEADERS = name=3DX-Forwarded-For][VALUE][/LISTMIMEHEADERS][/TEXT][/ELSE][!] >> [/!][/IF] >>=20 >> My suggestion is to = [LISTMIMEHEADERS][NAME]=3D[VALUE]
[/LISTMIMEHEADERS] and see if you = can find the visitor=E2=80=99s IPADDRESS and then work with that. >>=20 >>=20 >> Kind regards >>=20 >> Stuart Tremain >> IDFK Web Developments >> AUSTRALIA >> webdna@idfk.com.au >>=20 >>=20 >>=20 >>=20 >>=20 >>> On 4 Jul 2016, at 05:56, Donovan Brooke wrote: >>>=20 >>> My advice.. Don't listen to Ken and your WebDNA life will be much = better. :-).. He'll inevitably try to sell you bat guano anyway. :) >>>=20 >>> My opinion is that Palle has a point. This feature in WebDNA is a = major/crucial feature, that in the past has *always* performed the same. = Yes, the problem may be in the Mac OS of late, but a change like this = ideally should produce a clear explanation of how to fix it by WSC. On = the other hand, noting the resource limitation that Chris made public, = the answer could come from the community as well. >>>=20 >>> An instruction to just shut off the proxy, in my opinion, is = shallow.. At least until the end user is made aware of what this proxy = is for. >>>=20 >>> In other words, don't call someone pig headed, if you are one = yourself.=20 >>>=20 >>> The answer Palle is seeking, could help others as well. >>>=20 >>> D. Brooke Mobile >>>=20 >>> On Jul 3, 2016, at 1:05 PM, Kenneth Grome = wrote: >>>=20 >>>>> ... and if that i technical not possible - so be it. >>>>=20 >>>> It should be a simple matter for you to shut down your proxy >>>> server -- a solution we have twice recommended -- or configure it >>>> to pass through the real ip address. >>>>=20 >>>> Your proxy server is creating this problem, not WebDNA. >>>>=20 >>>> Regards, >>>> Kenneth Grome >>>> WebDNA Solutions >>>> http://www.webdnasolutions.com >>>> Web Database Systems and Linux Server Administration >>>> --------------------------------------------------------- >>>> This message is sent to you because you are subscribed to >>>> the mailing list . >>>> To unsubscribe, E-mail to: >>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>> Bug Reporting: support@webdna.us >>>=20 >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
Associated Messages, from the most recent to the oldest:
822 Hi Christophe This thread has been idle for a while now but I do think it is relevant = to revive it again. Have you had any thoughts about getting the original functionality = behind [ipaddress] to work as intended after the introduction of macOS = Sierra. I have made some investigation my self and I have not found any = easy (if any at all) solution to get the clients IP address using the = [ipaddress] function nor have I found any easy (if any) way to safely = disable the reverse proxy. I would naturally appreciate if the tag worked again since it is the = prerequisite to much code, other functions like [session], etc. = regardless of who made the actual change, WebNDA or Apple... I am looking forward to you reply and am in need :) /Palle > On 5 Jul 2016, at 13.02, Palle Bo Nielsen = wrote: >=20 > Hi Stuart >=20 > Thank you and I appreciate your example, which I understand. >=20 > /Palle >=20 >=20 >=20 >> On 04 Jul 2016, at 01:36, Stuart Tremain wrote: >>=20 >> After having worked with WebDNA on windows and now Linux in a number = of different hosting environments I have found different things = happening with [ipaddress] >>=20 >> Lately using Amazon with a load balancer I found that I needed to = look at the headers being sent back from the load balancer, in there I = found that the visitors IP address was being sent in a custom header = while [ipaddress] only returned the ipaddress of the load balancer. >>=20 >> Maybe if you are doing something a bit differently such as Palle is = you may find that you will have to write a custom function. >>=20 >> [text]VIPADDRESS=3D[LISTMIMEHEADERS = name=3DX-Forwarded-For][VALUE][/LISTMIMEHEADERS][/TEXT] >>=20 >> It changed again when I then used their CDN =E2=80=9CCloud Front=E2=80=9D= , this is my solution: >>=20 >> [IF ("[ListMIMEHeaders = name=3DUser-Agent][value][/ListMIMEHeaders]"=3D"Amazon CloudFront")][!] >> [/!][THEN][text]VIPADDRESS=3D[GREP = search=3D([^0-9\.])&replace=3D][MIDDLE = StartAfter=3D&EndBefore=3D,][LISTMIMEHEADERS = name=3DX-Forwarded-For][VALUE][/LISTMIMEHEADERS][/MIDDLE][/GREP][/TEXT][/T= HEN][!] >> [/!][ELSE][text]VIPADDRESS=3D[LISTMIMEHEADERS = name=3DX-Forwarded-For][VALUE][/LISTMIMEHEADERS][/TEXT][/ELSE][!] >> [/!][/IF] >>=20 >> My suggestion is to = [listmimeheaders][NAME]=3D[VALUE]
[/LISTMIMEHEADERS] and see if you = can find the visitor=E2=80=99s IPADDRESS and then work with that. >>=20 >>=20 >> Kind regards >>=20 >> Stuart Tremain >> IDFK Web Developments >> AUSTRALIA >> webdna@idfk.com.au >>=20 >>=20 >>=20 >>=20 >>=20 >>> On 4 Jul 2016, at 05:56, Donovan Brooke wrote: >>>=20 >>> My advice.. Don't listen to Ken and your WebDNA life will be much = better. :-).. He'll inevitably try to sell you bat guano anyway. :) >>>=20 >>> My opinion is that Palle has a point. This feature in WebDNA is a = major/crucial feature, that in the past has *always* performed the same. = Yes, the problem may be in the Mac OS of late, but a change like this = ideally should produce a clear explanation of how to fix it by WSC. On = the other hand, noting the resource limitation that Chris made public, = the answer could come from the community as well. >>>=20 >>> An instruction to just shut off the proxy, in my opinion, is = shallow.. At least until the end user is made aware of what this proxy = is for. >>>=20 >>> In other words, don't call someone pig headed, if you are one = yourself.=20 >>>=20 >>> The answer Palle is seeking, could help others as well. >>>=20 >>> D. Brooke Mobile >>>=20 >>> On Jul 3, 2016, at 1:05 PM, Kenneth Grome = wrote: >>>=20 >>>>> ... and if that i technical not possible - so be it. >>>>=20 >>>> It should be a simple matter for you to shut down your proxy >>>> server -- a solution we have twice recommended -- or configure it >>>> to pass through the real ip address. >>>>=20 >>>> Your proxy server is creating this problem, not WebDNA. >>>>=20 >>>> Regards, >>>> Kenneth Grome >>>> WebDNA Solutions >>>> http://www.webdnasolutions.com >>>> Web Database Systems and Linux Server Administration >>>> --------------------------------------------------------- >>>> This message is sent to you because you are subscribed to >>>> the mailing list . >>>> To unsubscribe, E-mail to: >>>> archives: http://mail.webdna.us/list/talk@webdna.us >>>> Bug Reporting: support@webdna.us >>>=20 >>> --------------------------------------------------------- >>> This message is sent to you because you are subscribed to >>> the mailing list . >>> To unsubscribe, E-mail to: >>> archives: http://mail.webdna.us/list/talk@webdna.us >>> Bug Reporting: support@webdna.us >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
Palle Bo Nielsen
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Mime Headers for Mail (1998)
[WebDNA] OT: Indexing PDF on iTools / apache2 (2008)
Laying an egg. (1998)
Opinion: [input] should be called [output] ... (1997)
RE:It just Does't add up!!! (1997)
Problem (1997)
# fields limited? (1997)
Brain Fade (2003)
Setting up WebCatalog with Retail Pro data (1996)
[WriteFile] problems (1997)
WebCatalog can't find database (1997)
Re:no [search] with NT (1997)
Email (1998)
Limitations on fields? Server is crashing (1997)
(2000)
(OT) Dual 2GHz G5 (2003)
webDNA engine creating duplicate lineitems?! (2004)
PCS Frames-Default page is solution! (1997)
Practice runs ? (1997)
New public beta available (1997)