|
Hello Marwa, Did you get a reply about this? We're also interested in a solution. Not sure how Google Maps works exactly, but one approach is to set up a proxy server which interrogates the HTTP_REFERER field in the request header, and only forwards the request to Geoserver if this reflects the domain from which your client was served. Of course, this could be spoofed, but it would prevent all but the most determined developer. In fact, we're thinking of using this technique to set up a Geoserver login session (to mimic a user/password entry), which would handle the authentication from then on. It would be interesting if anyone knew how the domain-specific authentication works for Google Maps....? Andy On 03/03/2011 12:24, marwa El-said wrote: Hello all, |
------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
