It sounds like you are running into issues with the "same origin policy" imposed on JavaScript by web browsers:
http://en.wikipedia.org/wiki/Same_origin_policy <http://en.wikipedia.org/wiki/Same_origin_policy>GeoServer has a basic file server built in, if you put the HTML page for your JavaScript in (GEOSERVER_DATA_DIR)/www/ then it should be on the same origin as the WFS service and you can avoid this issue. -- David Winslow OpenGeo - http://opengeo.org/ 2011/6/6 Luís de Sousa <[email protected]> > Ok, so by default Geoserver is not supposed to server WFS layers remotely. > > I'm following this guide: > > > http://www.gistutor.com/geoserver/21-intermediate-geoserver-tutorials/38-configuring-geoserver-proxy-for-public-and-remote-data-access.html > > Will report back on the results. Thank you, > > Luís > > > ------------------------------------------------------------------------------ > Simplify data backup and recovery for your virtual environment with > vRanger. > Installation's a snap, and flexible recovery options mean your data is > safe, > secure and there when you need it. Discover what all the cheering's about. > Get your free trial download today. > http://p.sf.net/sfu/quest-dev2dev2 > _______________________________________________ > Geoserver-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users >
------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2
_______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
