<br><br><div><span class="gmail_quote">On 7/13/07, <b class="gmail_sendername">P T Withington</b> <<a href="mailto:ptw@openlaszlo.org">ptw@openlaszlo.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
So the src attribute would still be the real source of the data?<br><br>Presumably the proxy needs to vet the requestee and the source being<br>requested so that it does not act as an 'open relay'?</blockquote><div>
<br><br>There's no really good way I can think of to do that, given that the app<br>source is readable to a pretty casual observer. Put the proxy should probably<br>have a default of "closed", and only speak to specific 3rd party hosts as configured in a config file.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I wonder if we should have a global proxy config file like [proxy.pac]<br>(<a href="http://wp.netscape.com/eng/mozilla/2.0/relnotes/demo/proxy-live.html">
http://wp.netscape.com/eng/mozilla/2.0/relnotes/demo/proxy-live.html</a>)<br><br>On 2007-07-13, at 12:25 EDT, Henry Minsky wrote:<br><br>> I recently ran into an issue when trying to deploy a SOLO app to a<br>> host
<br>> which is not running<br>> the LPS server. I need to access 3rd party data and images from a<br>> server,<br>> and due to security<br>> policy in Flash and DHTML runtimes, need a proxy server living on
<br>> the same<br>> host that my app is served from.<br>><br>> There have been a couple of different PHP HTTP proxies written, and<br>> I'd like<br>> to add support to our<br>> data API to specify an explicit URL for the proxy server. Currently
<br>> it is<br>> implicitly generated using<br>> LzBrowser.getBaseURL( ) as the url.<br>><br>> I propose adding a "proxyhost" attribute to dataset, which<br>> specifies the<br>> host to forward requests to.
<br>> HTTP requests would still be formatted using the existing LZX proxy<br>> protocol, so the server to<br>> which you point would be expected to look like an LZX server for<br>> purposes of<br>> requests which are marked
<br>> as lzt=data or lzt=media. However, it would not be necessary for<br>> the proxy<br>> server to support all the optional args<br>> such as cache control or header forwarding.<br>><br>> The syntax would look like this
<br>><br>> <dataset name="mydata" proxyhost="myproxy.php"/> for a relative url or<br>><br>> <dataset name="mydata" proxyhost="/myproxy.php"/> relative to host
<br>> server<br>> root directory<br>><br>> <dataset name="mydata" proxyhost="<a href="http://myhost.com/proxy/">http://myhost.com/proxy/</a><br>> myproxy.php"/><br>> for an absolute url (needs to be
<br>> on same host as app served from for default security policy of most<br>> browsers)<br>><br>> Another option would be some global canvas setting<br>><br>> <atttribute name="proxyhost" value="/myproxy.php"/>
<br>><br>> or<br>><br>> <canvas proxyhost="/myproxy.php"><br>><br>><br>><br>><br>><br>><br>><br>><br>><br>><br>> --<br>> Henry Minsky<br>> Software Architect
<br>> <a href="mailto:hminsky@laszlosystems.com">hminsky@laszlosystems.com</a><br><br></blockquote></div><br><br clear="all"><br>-- <br>Henry Minsky<br>Software Architect<br><a href="mailto:hminsky@laszlosystems.com">hminsky@laszlosystems.com
</a><br><br>