From: David O. <da...@qc...> - 2017-01-24 11:15:57
|
Ah... We do have checkforproxy enabled. So while it may hold true that a request can only have 1 peer, the X-Forwarded-For header could contain a list of proxies after the client address. Makes sense - thanks On 24 January 2017 at 10:32, Gustaf Neumann <ne...@wu...> wrote: > Am 24.01.17 um 11:02 schrieb David Osborne: > > Can anyone come up with a scenario where a request could have 2 peer IP > addresses? > > We occasionally see entries in the naviserver access logs like this one > and I'm really not sure what to make of them: > > 10.x.x.x, 37.x.x.x - - [23/Jan/2017:07:55:55 +0000] "GET / HTTP/1.0" 500 671 "https://www.domain.co.uk/index.html" "Opera/9.80 (Android; Opera Mini/7.7.40394/37.9311; U; en) Presto/2.12.423 Version/12.16" > > Maybe running behind a proxy and/or parameter "checkforproxy" of > ns/server/${server}/module/nslog set to true? > When this parameter is it, it will produce an entry as provided by > X-Forwarded-For. > > -g > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > naviserver-devel mailing list > nav...@li... > https://lists.sourceforge.net/lists/listinfo/naviserver-devel > > -- David Osborne Qcode Software Limited http://www.qcode.co.uk T: +44 (0)1463 896484 |