Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly

This WebDNA talk-list message is from

2016


It keeps the original formatting.
numero = 113236
interpreted = N
texte = 824 --Apple-Mail=_42A4CFAC-9C57-4214-BFBB-6041C3DE651D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Michael I understand and only wanted to learn if there was anything going on = behind the WebDNA lines, hense my question. /Palle > On 6 Dec 2016, at 04.26, Michael Davis wrote: >=20 > Palle, >=20 > Have you looked at [listmimeheaders] to see if the Apple Server proxy = is sending anything useful, such as an X-Forwarded-For header? =20 > This really isn't a WebDNA issue. If you put a web server behind a = proxy, you no longer have visibility directly with the client. Whether = it's squid or varnish or an Amazon load balancer, all clients appear to = come from one or a couple addresses, that of the proxy(s). It's = generally up to the proxy configuration to include a header with address = information that would otherwise be lost. =20 >=20 > MD >=20 > PS, anyone else getting mail from this list in corrupted/garbled form = with all the mime line endings like below? >=20 >> On Dec 5, 2016, at 1:44 PM, Palle Bo Nielsen = > wrote: >>=20 >> This thread has been idle for a while now but I do think it is = relevant =3D >> to revive it again. >>=20 >> Have you had any thoughts about getting the original functionality =3D >> behind [ipaddress] to work as intended after the introduction of = macOS =3D >> Sierra. I have made some investigation my self and I have not found = any =3D >> easy (if any at all) solution to get the clients IP address using the = =3D >> [ipaddress] function nor have I found any easy (if any) way to safely = =3D >> disable the reverse proxy. >>=20 >> I would naturally appreciate if the tag worked again since it is the = =3D >> prerequisite to much code, other functions like [Session], etc. =3D >> regardless of who made the actual change, WebNDA or Apple... >>=20 >> I am looking forward to you reply and am in need :) >>=20 >> /Palle >>=20 >>=20 >>=20 >>> On 5 Jul 2016, at 13.02, Palle Bo Nielsen > =3D >> wrote: >>> =3D20 >>> Hi Stuart >>> =3D20 >>> Thank you and I appreciate your example, which I understand. >>> =3D20 >>> /Palle >>> =3D20 >>> =3D20 >>> =3D20 >>>> On 04 Jul 2016, at 01:36, Stuart Tremain > wrote: >>>> =3D20 >>>> After having worked with WebDNA on windows and now Linux in a = number =3D >> of different hosting environments I have found different things =3D >> happening with [IPADDRESS] >>>> =3D20 >>>> Lately using Amazon with a load balancer I found that I needed to =3D= >> look at the headers being sent back from the load balancer, in there = I =3D >> found that the visitors IP address was being sent in a custom header = =3D >> while [IPADDRESS] only returned the ipaddress of the load balancer. >>>> =3D20 >>>> Maybe if you are doing something a bit differently such as Palle is = =3D >> you may find that you will have to write a custom function. >>>> =3D20 >>>> [TEXT]VIPADDRESS=3D3D[LISTMIMEHEADERS =3D >> name=3D3DX-Forwarded-For][VALUE][/LISTMIMEHEADERS][/TEXT] >>>> =3D20 >>>> It changed again when I then used their CDN =3DE2=3D80=3D9CCloud = Front=3DE2=3D80=3D9D=3D >> , this is my solution: >>>> =3D20 >>>> [IF ("[ListMIMEHeaders =3D >> name=3D3DUser-Agent][value][/ListMIMEHeaders]"=3D3D"Amazon = CloudFront")][!] >>>> [/!][THEN][TEXT]VIPADDRESS=3D3D[GREP =3D >> search=3D3D([^0-9\.])&replace=3D3D][MIDDLE =3D >> StartAfter=3D3D&EndBefore=3D3D,][LISTMIMEHEADERS =3D >> = name=3D3DX-Forwarded-For][VALUE][/LISTMIMEHEADERS][/MIDDLE][/GREP][/TEXT][= /T=3D >> HEN][!] >>>> [/!][ELSE][TEXT]VIPADDRESS=3D3D[LISTMIMEHEADERS =3D >> name=3D3DX-Forwarded-For][VALUE][/LISTMIMEHEADERS][/TEXT][/ELSE][!] >>>> [/!][/IF] >>>> =3D20 >>>> My suggestion is to =3D >> [LISTMIMEHEADERS][NAME]=3D3D[VALUE]
[/LISTMIMEHEADERS] and see if = you =3D >> can find the visitor=3DE2=3D80=3D99s IPADDRESS and then work with = that. >>>> =3D20 >>>> =3D20 >>>> Kind regards >>>> =3D20 >>>> Stuart Tremain >>>> IDFK Web Developments >>>> AUSTRALIA >>>> webdna@idfk.com.au >>>> =3D20 >>>> =3D20 >>>> =3D20 >>>> =3D20 >>>> =3D20 >>>>> On 4 Jul 2016, at 05:56, Donovan Brooke wrote: >>>>> =3D20 >>>>> My advice.. Don't listen to Ken and your WebDNA life will be much = =3D >> better. :-).. He'll inevitably try to sell you bat guano anyway. :) >>>>> =3D20 >>>>> My opinion is that Palle has a point. This feature in WebDNA is a = =3D >> major/crucial feature, that in the past has *always* performed the = same. =3D >> Yes, the problem may be in the Mac OS of late, but a change like this = =3D >> ideally should produce a clear explanation of how to fix it by WSC. = On =3D >> the other hand, noting the resource limitation that Chris made = public, =3D >> the answer could come from the community as well. >>>>> =3D20 >>>>> An instruction to just shut off the proxy, in my opinion, is =3D >> shallow.. At least until the end user is made aware of what this = proxy =3D >> is for. >>>>> =3D20 >>>>> In other words, don't call someone pig headed, if you are one =3D >> yourself.=3D20 >>>>> =3D20 >>>>> The answer Palle is seeking, could help others as well. >>>>> =3D20 >>>>> D. Brooke Mobile >>>>> =3D20 >>>>> On Jul 3, 2016, at 1:05 PM, Kenneth Grome > =3D >> wrote: >>>>> =3D20 >>>>>>> ... and if that i technical not possible - so be it. >>>>>> =3D20 >>>>>> 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. >>>>>> =3D20 >>>>>> Your proxy server is creating this problem, not WebDNA. >>>>>> =3D20 >>>>>> 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 >>>>> =3D20 >>>>> --------------------------------------------------------- >>>>> 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 >>>> =3D20 >>>> --------------------------------------------------------- >>>> 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 >>> =3D20 >>> --------------------------------------------------------- >>> 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 --Apple-Mail=_42A4CFAC-9C57-4214-BFBB-6041C3DE651D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
Hi Michael

I understand and only wanted to learn = if there was anything going on behind the WebDNA lines, hense my = question.

/Palle


On = 6 Dec 2016, at 04.26, Michael Davis <admin@network13.net>= wrote:

Palle,

Have you looked at = [listmimeheaders] to see if the Apple Server proxy is sending anything = useful, such as an X-Forwarded-For header?  
This really isn't a WebDNA issue.  If you put a web = server behind a proxy, you no longer have visibility directly with the = client.  Whether it's squid or varnish or an Amazon load balancer, =  all clients appear to come from one or a couple addresses, that of = the proxy(s).  It's generally up to the proxy configuration to = include a header with address information that would otherwise be lost. =  

MD

PS, anyone else getting mail from this list in = corrupted/garbled form with all the mime line endings like = below?

On Dec 5, 2016, at 1:44 PM, = Palle Bo Nielsen <powerpalle@powerpalle.dk> wrote:

This = thread has been idle for a while now but I do think it is relevant =3D
to revive it again.

Have you had = any thoughts about getting the original functionality =3D
behind [ipaddress] to work as intended after the introduction = of macOS =3D
Sierra. I have made some investigation my = self and I have not found any =3D
easy (if any at all) = solution to get the clients IP address using the =3D
[ipaddress] function nor have I found any easy (if any) way = to safely =3D
disable the reverse proxy.

I would naturally appreciate if the tag worked again since it = is the =3D
prerequisite to much code, other functions like = [Session], etc. =3D
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 <powerpalle@powerpalle.dk> =3D
wrote:
=3D20
Hi Stuart
=3D20
Thank you and I appreciate your example, which I = understand.
=3D20
/Palle
=3D20=3D20
=3D20
On 04 Jul 2016, at 01:36, Stuart Tremain <webdna@idfk.com.au> = wrote:
=3D20
After having worked with WebDNA = on windows and now Linux in a number =3D
of different hosting environments I = have found different things =3D
happening with = [IPADDRESS]
=3D20
Lately using Amazon with a = load balancer I found that I needed to =3D
look at the headers being sent back = from the load balancer, in there I =3D
found that the = visitors IP address was being sent in a custom header =3D
while [IPADDRESS] only returned the ipaddress of the load = balancer.
=3D20
Maybe if you are doing = something a bit differently such as Palle is =3D
you may find that you will have to = write a custom function.
=3D20
[TEXT]VIPADDRESS=3D3D[LISTMIMEHEADERS =3D
name=3D3DX-Forwarded-For][VALUE][/LIS= TMIMEHEADERS][/TEXT]
=3D20
It = changed again when I then used their CDN =3DE2=3D80=3D9CCloud = Front=3DE2=3D80=3D9D=3D
, this = is my solution:
=3D20
[IF = ("[ListMIMEHeaders =3D
name=3D3DUser-Agent][value][/ListMIME= Headers]"=3D3D"Amazon CloudFront")][!]
= [/!][THEN][TEXT]VIPADDRESS=3D3D[GREP =3D
search=3D3D([^0-9\.])&replace=3D3= D][MIDDLE =3D
StartAfter=3D3D&EndBefore=3D3D,][LISTMIMEHEADERS =3D
name=3D3DX-Forwarded-For][VALUE][/LISTMIMEHEADERS][/MIDDLE][/GR= EP][/TEXT][/T=3D
HEN][!]
= [/!][ELSE][TEXT]VIPADDRESS=3D3D[LISTMIMEHEADERS =3D
name=3D3DX-Forwarded-For][VALUE][/LIS= TMIMEHEADERS][/TEXT][/ELSE][!]
[/!][/IF]
=3D20
My suggestion is to =3D
[LISTMIMEHEADERS][NAME]=3D3D[VALUE]&l= t;br>[/LISTMIMEHEADERS] and see if you =3D
can find the = visitor=3DE2=3D80=3D99s IPADDRESS and then work with that.
=3D20
=3D20
Kind regards
=3D20
Stuart Tremain
IDFK Web = Developments
AUSTRALIA
webdna@idfk.com.au
=3D20
=3D20
=3D20
=3D20
=3D20
On 4 Jul 2016, at 05:56, Donovan Brooke <dbrooke@euca.us> = wrote:
=3D20
My advice.. Don't listen to Ken = and your WebDNA life will be much =3D
better. :-).. He'll = inevitably try to sell you bat guano anyway. :)
=3D20
My opinion is that Palle = has a point. This feature in WebDNA is a =3D
major/crucial feature, = that in the past has *always* performed the same. =3D
Yes, = the problem may be in the Mac OS of late, but a change like this =3D
ideally should produce a clear explanation of how to fix it = by WSC. On =3D
the other hand, noting the resource = limitation that Chris made public, =3D
the answer could = come from the community as well.
=3D20
An instruction to just shut off the = proxy, in my opinion, is =3D
shallow.. At least = until the end user is made aware of what this proxy =3D
is = for.
=3D20
In other words, don't call someone pig headed, if you are one = =3D
yourself.=3D20
=3D20
The = answer Palle is seeking, could help others as well.
=3D20D. Brooke Mobile
=3D20
On Jul 3, = 2016, at 1:05 PM, Kenneth Grome <ken@webdnasolutions.com> =3D
wrote:
=3D20
... and if that i technical not possible - so be it.
=3D20
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.
=3D20
Your proxy server = is creating this problem, not WebDNA.
=3D20
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 <talk@webdna.us>.
To unsubscribe, E-mail = to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug= Reporting: support@webdna.us
=3D20
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail = to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug= Reporting: support@webdna.us
=3D20
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail = to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug= Reporting: support@webdna.us
=3D20
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail = to: <talk-leave@webdna.us>
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 <talk@webdna.us>.
To unsubscribe, E-mail = to: <talk-leave@webdna.us>
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
= --------------------------------------------------------- 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 --Apple-Mail=_42A4CFAC-9C57-4214-BFBB-6041C3DE651D-- . Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Palle Bo Nielsen 2016)
  2. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Michael Davis 2016)
  3. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Palle Bo Nielsen 2016)
  4. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Palle Bo Nielsen 2016)
  5. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Stuart Tremain 2016)
  6. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (christophe.billiottet@webdna.us 2016)
  7. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Bob Minor 2016)
  8. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Palle Bo Nielsen 2016)
  9. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Donovan Brooke 2016)
  10. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Kenneth Grome 2016)
  11. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Palle Bo Nielsen 2016)
  12. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Kenneth Grome 2016)
  13. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Palle Bo Nielsen 2016)
  14. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Palle Bo Nielsen 2016)
  15. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Bob Minor 2016)
  16. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Kenneth Grome 2016)
  17. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Palle Bo Nielsen 2016)
  18. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (christophe.billiottet@webdna.us 2016)
  19. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Palle Bo Nielsen 2016)
  20. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Donovan Brooke 2016)
  21. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Office 2016)
  22. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Palle Bo Nielsen 2016)
  23. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Donovan Brooke 2016)
  24. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Matthew Perosi 2016)
  25. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (christophe.billiottet@webdna.us 2016)
  26. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Palle Bo Nielsen 2016)
  27. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (christophe.billiottet@webdna.us 2016)
  28. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Palle Bo Nielsen 2016)
  29. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (christophe.billiottet@webdna.us 2016)
  30. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (Palle Bo Nielsen 2016)
  31. Re: [WebDNA] [ipaddress] - [RealIP] - Not working properly (christophe.billiottet@webdna.us 2016)
  32. [WebDNA] [ipaddress] - [RealIP] - Not working properly (Palle Bo Nielsen 2016)
824 --Apple-Mail=_42A4CFAC-9C57-4214-BFBB-6041C3DE651D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi Michael I understand and only wanted to learn if there was anything going on = behind the WebDNA lines, hense my question. /Palle > On 6 Dec 2016, at 04.26, Michael Davis wrote: >=20 > Palle, >=20 > Have you looked at [listmimeheaders] to see if the Apple Server proxy = is sending anything useful, such as an X-Forwarded-For header? =20 > This really isn't a WebDNA issue. If you put a web server behind a = proxy, you no longer have visibility directly with the client. Whether = it's squid or varnish or an Amazon load balancer, all clients appear to = come from one or a couple addresses, that of the proxy(s). It's = generally up to the proxy configuration to include a header with address = information that would otherwise be lost. =20 >=20 > MD >=20 > PS, anyone else getting mail from this list in corrupted/garbled form = with all the mime line endings like below? >=20 >> On Dec 5, 2016, at 1:44 PM, Palle Bo Nielsen = > wrote: >>=20 >> This thread has been idle for a while now but I do think it is = relevant =3D >> to revive it again. >>=20 >> Have you had any thoughts about getting the original functionality =3D >> behind [ipaddress] to work as intended after the introduction of = macOS =3D >> Sierra. I have made some investigation my self and I have not found = any =3D >> easy (if any at all) solution to get the clients IP address using the = =3D >> [ipaddress] function nor have I found any easy (if any) way to safely = =3D >> disable the reverse proxy. >>=20 >> I would naturally appreciate if the tag worked again since it is the = =3D >> prerequisite to much code, other functions like [session], etc. =3D >> regardless of who made the actual change, WebNDA or Apple... >>=20 >> I am looking forward to you reply and am in need :) >>=20 >> /Palle >>=20 >>=20 >>=20 >>> On 5 Jul 2016, at 13.02, Palle Bo Nielsen > =3D >> wrote: >>> =3D20 >>> Hi Stuart >>> =3D20 >>> Thank you and I appreciate your example, which I understand. >>> =3D20 >>> /Palle >>> =3D20 >>> =3D20 >>> =3D20 >>>> On 04 Jul 2016, at 01:36, Stuart Tremain > wrote: >>>> =3D20 >>>> After having worked with WebDNA on windows and now Linux in a = number =3D >> of different hosting environments I have found different things =3D >> happening with [ipaddress] >>>> =3D20 >>>> Lately using Amazon with a load balancer I found that I needed to =3D= >> look at the headers being sent back from the load balancer, in there = I =3D >> found that the visitors IP address was being sent in a custom header = =3D >> while [ipaddress] only returned the ipaddress of the load balancer. >>>> =3D20 >>>> Maybe if you are doing something a bit differently such as Palle is = =3D >> you may find that you will have to write a custom function. >>>> =3D20 >>>> [text]VIPADDRESS=3D3D[LISTMIMEHEADERS =3D >> name=3D3DX-Forwarded-For][VALUE][/LISTMIMEHEADERS][/TEXT] >>>> =3D20 >>>> It changed again when I then used their CDN =3DE2=3D80=3D9CCloud = Front=3DE2=3D80=3D9D=3D >> , this is my solution: >>>> =3D20 >>>> [IF ("[ListMIMEHeaders =3D >> name=3D3DUser-Agent][value][/ListMIMEHeaders]"=3D3D"Amazon = CloudFront")][!] >>>> [/!][THEN][text]VIPADDRESS=3D3D[GREP =3D >> search=3D3D([^0-9\.])&replace=3D3D][MIDDLE =3D >> StartAfter=3D3D&EndBefore=3D3D,][LISTMIMEHEADERS =3D >> = name=3D3DX-Forwarded-For][VALUE][/LISTMIMEHEADERS][/MIDDLE][/GREP][/TEXT][= /T=3D >> HEN][!] >>>> [/!][ELSE][text]VIPADDRESS=3D3D[LISTMIMEHEADERS =3D >> name=3D3DX-Forwarded-For][VALUE][/LISTMIMEHEADERS][/TEXT][/ELSE][!] >>>> [/!][/IF] >>>> =3D20 >>>> My suggestion is to =3D >> [listmimeheaders][NAME]=3D3D[VALUE]
[/LISTMIMEHEADERS] and see if = you =3D >> can find the visitor=3DE2=3D80=3D99s IPADDRESS and then work with = that. >>>> =3D20 >>>> =3D20 >>>> Kind regards >>>> =3D20 >>>> Stuart Tremain >>>> IDFK Web Developments >>>> AUSTRALIA >>>> webdna@idfk.com.au >>>> =3D20 >>>> =3D20 >>>> =3D20 >>>> =3D20 >>>> =3D20 >>>>> On 4 Jul 2016, at 05:56, Donovan Brooke wrote: >>>>> =3D20 >>>>> My advice.. Don't listen to Ken and your WebDNA life will be much = =3D >> better. :-).. He'll inevitably try to sell you bat guano anyway. :) >>>>> =3D20 >>>>> My opinion is that Palle has a point. This feature in WebDNA is a = =3D >> major/crucial feature, that in the past has *always* performed the = same. =3D >> Yes, the problem may be in the Mac OS of late, but a change like this = =3D >> ideally should produce a clear explanation of how to fix it by WSC. = On =3D >> the other hand, noting the resource limitation that Chris made = public, =3D >> the answer could come from the community as well. >>>>> =3D20 >>>>> An instruction to just shut off the proxy, in my opinion, is =3D >> shallow.. At least until the end user is made aware of what this = proxy =3D >> is for. >>>>> =3D20 >>>>> In other words, don't call someone pig headed, if you are one =3D >> yourself.=3D20 >>>>> =3D20 >>>>> The answer Palle is seeking, could help others as well. >>>>> =3D20 >>>>> D. Brooke Mobile >>>>> =3D20 >>>>> On Jul 3, 2016, at 1:05 PM, Kenneth Grome > =3D >> wrote: >>>>> =3D20 >>>>>>> ... and if that i technical not possible - so be it. >>>>>> =3D20 >>>>>> 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. >>>>>> =3D20 >>>>>> Your proxy server is creating this problem, not WebDNA. >>>>>> =3D20 >>>>>> 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 >>>>> =3D20 >>>>> --------------------------------------------------------- >>>>> 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 >>>> =3D20 >>>> --------------------------------------------------------- >>>> 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 >>> =3D20 >>> --------------------------------------------------------- >>> 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 --Apple-Mail=_42A4CFAC-9C57-4214-BFBB-6041C3DE651D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
Hi Michael

I understand and only wanted to learn = if there was anything going on behind the WebDNA lines, hense my = question.

/Palle


On = 6 Dec 2016, at 04.26, Michael Davis <admin@network13.net>= wrote:

Palle,

Have you looked at = [listmimeheaders] to see if the Apple Server proxy is sending anything = useful, such as an X-Forwarded-For header?  
This really isn't a WebDNA issue.  If you put a web = server behind a proxy, you no longer have visibility directly with the = client.  Whether it's squid or varnish or an Amazon load balancer, =  all clients appear to come from one or a couple addresses, that of = the proxy(s).  It's generally up to the proxy configuration to = include a header with address information that would otherwise be lost. =  

MD

PS, anyone else getting mail from this list in = corrupted/garbled form with all the mime line endings like = below?

On Dec 5, 2016, at 1:44 PM, = Palle Bo Nielsen <powerpalle@powerpalle.dk> wrote:

This = thread has been idle for a while now but I do think it is relevant =3D
to revive it again.

Have you had = any thoughts about getting the original functionality =3D
behind [ipaddress] to work as intended after the introduction = of macOS =3D
Sierra. I have made some investigation my = self and I have not found any =3D
easy (if any at all) = solution to get the clients IP address using the =3D
[ipaddress] function nor have I found any easy (if any) way = to safely =3D
disable the reverse proxy.

I would naturally appreciate if the tag worked again since it = is the =3D
prerequisite to much code, other functions like = [session], etc. =3D
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 <powerpalle@powerpalle.dk> =3D
wrote:
=3D20
Hi Stuart
=3D20
Thank you and I appreciate your example, which I = understand.
=3D20
/Palle
=3D20=3D20
=3D20
On 04 Jul 2016, at 01:36, Stuart Tremain <webdna@idfk.com.au> = wrote:
=3D20
After having worked with WebDNA = on windows and now Linux in a number =3D
of different hosting environments I = have found different things =3D
happening with = [ipaddress]
=3D20
Lately using Amazon with a = load balancer I found that I needed to =3D
look at the headers being sent back = from the load balancer, in there I =3D
found that the = visitors IP address was being sent in a custom header =3D
while [ipaddress] only returned the ipaddress of the load = balancer.
=3D20
Maybe if you are doing = something a bit differently such as Palle is =3D
you may find that you will have to = write a custom function.
=3D20
[text]VIPADDRESS=3D3D[LISTMIMEHEADERS =3D
name=3D3DX-Forwarded-For][VALUE][/LIS= TMIMEHEADERS][/TEXT]
=3D20
It = changed again when I then used their CDN =3DE2=3D80=3D9CCloud = Front=3DE2=3D80=3D9D=3D
, this = is my solution:
=3D20
[IF = ("[ListMIMEHeaders =3D
name=3D3DUser-Agent][value][/ListMIME= Headers]"=3D3D"Amazon CloudFront")][!]
= [/!][THEN][text]VIPADDRESS=3D3D[GREP =3D
search=3D3D([^0-9\.])&replace=3D3= D][MIDDLE =3D
StartAfter=3D3D&EndBefore=3D3D,][LISTMIMEHEADERS =3D
name=3D3DX-Forwarded-For][VALUE][/LISTMIMEHEADERS][/MIDDLE][/GR= EP][/TEXT][/T=3D
HEN][!]
= [/!][ELSE][text]VIPADDRESS=3D3D[LISTMIMEHEADERS =3D
name=3D3DX-Forwarded-For][VALUE][/LIS= TMIMEHEADERS][/TEXT][/ELSE][!]
[/!][/IF]
=3D20
My suggestion is to =3D
[listmimeheaders][NAME]=3D3D[VALUE]&l= t;br>[/LISTMIMEHEADERS] and see if you =3D
can find the = visitor=3DE2=3D80=3D99s IPADDRESS and then work with that.
=3D20
=3D20
Kind regards
=3D20
Stuart Tremain
IDFK Web = Developments
AUSTRALIA
webdna@idfk.com.au
=3D20
=3D20
=3D20
=3D20
=3D20
On 4 Jul 2016, at 05:56, Donovan Brooke <dbrooke@euca.us> = wrote:
=3D20
My advice.. Don't listen to Ken = and your WebDNA life will be much =3D
better. :-).. He'll = inevitably try to sell you bat guano anyway. :)
=3D20
My opinion is that Palle = has a point. This feature in WebDNA is a =3D
major/crucial feature, = that in the past has *always* performed the same. =3D
Yes, = the problem may be in the Mac OS of late, but a change like this =3D
ideally should produce a clear explanation of how to fix it = by WSC. On =3D
the other hand, noting the resource = limitation that Chris made public, =3D
the answer could = come from the community as well.
=3D20
An instruction to just shut off the = proxy, in my opinion, is =3D
shallow.. At least = until the end user is made aware of what this proxy =3D
is = for.
=3D20
In other words, don't call someone pig headed, if you are one = =3D
yourself.=3D20
=3D20
The = answer Palle is seeking, could help others as well.
=3D20D. Brooke Mobile
=3D20
On Jul 3, = 2016, at 1:05 PM, Kenneth Grome <ken@webdnasolutions.com> =3D
wrote:
=3D20
... and if that i technical not possible - so be it.
=3D20
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.
=3D20
Your proxy server = is creating this problem, not WebDNA.
=3D20
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 <talk@webdna.us>.
To unsubscribe, E-mail = to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug= Reporting: support@webdna.us
=3D20
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail = to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug= Reporting: support@webdna.us
=3D20
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail = to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug= Reporting: support@webdna.us
=3D20
---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdna.us>.
To unsubscribe, E-mail = to: <talk-leave@webdna.us>
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 <talk@webdna.us>.
To unsubscribe, E-mail = to: <talk-leave@webdna.us>
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
= --------------------------------------------------------- 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 --Apple-Mail=_42A4CFAC-9C57-4214-BFBB-6041C3DE651D-- . 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:

Replto in [SendMail] (2000) searching for not-a-number (2003) RE: ShowNext Command (1997) Sending mail (2001) Generating and appending SKU to a db automatically (1998) Need help with emailer- 2 issues (1997) Exposure Opportunity....! (1999) Webdna 5.0 reference documentation (2003) Thanks Grant (1997) European dates (1998) [WebDNA] Secure Cookies (2009) [WebDNA] Error 500 with SUMM=T (2017) [shownext] and sort (1998) PIXO support (1997) eMail volume (2000) Suggestions for Topics to be covered in an Advanced WebDNACourse... (1998) WebCatalog2 Feature Feedback (1996) Logging purchases (1997) Zipcodes (1998) Hiding HTML and page breaks (1997)