Hi Shawn,
It looks like that solution is using filtering at the container level
(i.e., Tomcat). You might be able to change the <url-pattern> to be
/web/* instead of *. That should prevent access to the /web/* pages
while leaving access to /ows/*,/wfs/*, etc. endpoints.
Cheers,
Jim
On 06/07/2016 05:12 PM, Shawn Stanley wrote:
hello
I found the answer to this question in the following archived post,
https://sourceforge.net/p/geoserver/mailman/message/30830992/, and it
worked insofar as the access to the admin controls was successfully
restricted. However, the webmap is now not showing any data if I am
not accessing it from the nominated ip address.
Has anybody else come up against this?
regards
shawn
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
