[jira] [Resolved] (WICKET-5365) AtmosphereBehavior should also log X-Forwarded-For

["Martin Grigorov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-5365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-5365.
-------------------------------------

    Resolution: Won't Fix
      Assignee:     (was: Emond Papegaaij)

You can use org.apache.wicket.protocol.http.servlet.XForwardedRequestWrapperFactory. That will handle this automatically for you.

> AtmosphereBehavior should also log X-Forwarded-For
> --------------------------------------------------
>
>                 Key: WICKET-5365
>                 URL: https://issues.apache.org/jira/browse/WICKET-5365
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-atmosphere
>    Affects Versions: 6.8.0
>         Environment: nginx
>            Reporter: Hendy Irawan
>            Priority: Minor
>
> Servlet/Wicket apps are usually deployed behind a reverse proxy such as nginx. AtmosphereBehavior logs should also include X-Forwarded-For header (when it exists), in addition to remote_host, e.g. :
> {code}
> logger	  	org.apache.wicket.atmosphere.AtmosphereBehavior
> message	  	Suspending the streaming response from ip 127.0.0.1:41992
> logger	  	org.apache.wicket.atmosphere.AtmosphereBehavior
> message	  	streaming connection dropped from ip 127.0.0.1:41850
> logger	  	org.apache.wicket.atmosphere.AtmosphereBehavior
> message	  	Resuming the websocket response from ip 127.0.0.1:41360
> {code}



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)