https://bz.apache.org/bugzilla/show_bug.cgi?id=58433
--- Comment #4 from Karl von Randow <k...@xk72.com> --- We have encountered a similar issue. We have used the RemoteIpValve in our Context, which works well in our use cases (we didn't encounter your issue). However it does not work for error pages. It appears that error pages are handled after exiting from RemoteIpValve, in which case the Request settings have been reverted to their original values. On our error pages we still want to be able to test request.isSecure(), for example, to know whether to output secure or insecure URLs. Apologies for the tangent; I believe our issue would be solved by handling this in the adapter instead. Maybe this additional issues lends some weight to investigating that? Otherwise perhaps some advice? (We seem to be able to workaround the issue by using RemoteIpValve on the Engine instead, but we'd prefer to use it at the Context level). -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
