The OpenLayers example script proxy.cgi is not designed to solve this problem.
ProxyPass in Apache is a way to solve this problem, but won't really help you if your webserver is IIS; I presume IIS has similar proxying capabilities. Proxy.cgi is used to solve a different problem; if your OpenLayers content is hosted on the same host/port/scheme as your geo server, then you don't need it. -- Chris On May 22, 2011, at 4:16 PM, ext Mustafa646 wrote: > what is difference between proxypass and proxy.cgi ? why we use them? > > my OL application and Geoserver are both on same production server and i can > access geoserver from outside world at http://93.45.32.11:8080/geoserver/web > when Port 8080 is open in firewall. But, If port 8080 is closed, then i > could not access http://93.45.32.11/geoserver/web. > > Now, for accessing http://93.45.32.11/geoserver/web at port 80 (IIS is also > at 80), whether i need proxypass or proxy.cgi ? > i am confused between the two. What is the easiest and best solution so that > i can access Geoserver at port 80 from outside world? > > -- > View this message in context: > http://osgeo-org.1803224.n2.nabble.com/proxypass-and-Proxy-cgi-tp6392306p6392306.html > Sent from the OpenLayers Users mailing list archive at Nabble.com. > _______________________________________________ > Users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/openlayers-users _______________________________________________ Users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-users
