[OpenLayers-Users] free proxy wfs

Sat Dec 21 02:39:12 PST 2013

The answer to your question is that there is no need for a proxy there:
The webpage with the JavaScript is served from the same domain as the WFS
services that are requested by this JS, there is therefore no cross-domain
security issue, and therefore no need for a proxy...

To reproduce this, you should do the same: serve the page with the
OpenLayers script from the same domain as the WFS service is served from.

Barend

--
Barend Köbben 
ITC - University of Twente
PO Box 217, 7500AE Enschede (The Netherlands)
+31-(0)53 4874 253
@barendkobben

On 20-12-13 09:37, "Mario Nuñez Jimenez" <mario.nunez at atos.net> wrote:

>Sorry I really appreciate your help but I think I am getting lost with
>this discussion. The main question from my side is:
>Why "http://demo.opengeo.org/geoserver/wfs" works for me without any
>proxy from my side?
>I want to reproduce that if possible.
>
>I work with partners and sadly I don't know too much about their tasks, I
>only know that they are using a C++ standalone that includes a server and
>a web browser embebbed. So the idea is to be able to load in that web
>browser the openlayers web application locally but the OGC services are
>accessed remotely since they are hosted by my corporation host.
>
>So if he is not able to deploy a proxy in their embebbed server then the
>WFS couldn't be reached.
>That is the problem...
>
>
>-----Original Message-----
>From: openlayers-users-bounces at lists.osgeo.org
>[mailto:openlayers-users-bounces at lists.osgeo.org] On Behalf Of Phil
>Scadden
>Sent: martes, 17 de diciembre de 2013 21:52
>To: openlayers-users at lists.osgeo.org
>Subject: Re: [OpenLayers-Users] free proxy wfs
>
>
>
>> Anyway the decision is not mine, I have to provide a working web client
>>bringing the functionality of modify features, so I need a WFS-t in the
>>backend. Moreover I need to provide a wfs-t accessible without a proxy
>>for architecture reasons since the web browser and the web server will
>>be embebbed in a C++ standalone application and we cannot modify the web
>>server to host  a proxy.
>
>The need for a proxy is dictated by security features of the browser.
>Most browsers will not do cross-domain XHR for very very good reasons.
>Its a pretty strange server that cant host a proxy. What is the servlet
>container that hosts your the WFS server?(and why cant the proxy live in
>that?). If the only WFS features you are dealing are hosted on embedded
>server, then you may be able to configure so request is not cross-domain.
>Might also depend on what exactly this embedded web browser actually is.
>The alternative would be protocol.script but you will be writing a lot of
>code to work around its limitations. Effective web apps work to principle
>of having the server do most of the computing so I am curious as to how
>serverside works for your application.  I would have to say that using
>embedded web-server and browser + OL for a standalone C# mapping
>application is a pretty strange choice. OL has to work around web
>limitations that simply dont exist to a standalone C# application.
>
>Notice: This email and any attachments are confidential.
>If received in error please destroy and immediately notify us.
>Do not copy or disclose the contents.
>
>_______________________________________________
>Users mailing list
>Users at lists.osgeo.org
>http://lists.osgeo.org/mailman/listinfo/openlayers-users
>------------------------------------------------------------------
>This e-mail and the documents attached are confidential and intended
>solely for the addressee; it may also be privileged. If you receive
>this e-mail in error, please notify the sender immediately and destroy
>it. 
>As its integrity cannot be secured on the Internet, the Atos
>group liability cannot be triggered for the message content. Although
>the sender endeavours to maintain a computer virus-free network,
>the sender does not warrant that this transmission is virus-free and
>will not be liable for any damages resulting from any virus transmitted.
>
>Este mensaje y los ficheros adjuntos pueden contener informacion
>confidencial 
>destinada solamente a la(s) persona(s) mencionadas anteriormente
>pueden estar protegidos por secreto profesional.
>Si usted recibe este correo electronico por error, gracias por informar
>inmediatamente al remitente y destruir el mensaje.
>Al no estar asegurada la integridad de este mensaje sobre la red, Atos
>no se hace responsable por su contenido. Su contenido no constituye
>ningun 
>compromiso para el grupo Atos, salvo ratificacion escrita por ambas
>partes. 
>Aunque se esfuerza al maximo por mantener su red libre de virus, el
>emisor 
>no puede garantizar nada al respecto y no sera responsable de
>cualesquiera 
>danos que puedan resultar de una transmision de virus.
>------------------------------------------------------------------
>_______________________________________________
>Users mailing list
>Users at lists.osgeo.org
>http://lists.osgeo.org/mailman/listinfo/openlayers-users