[Laszlo-dev] proposal for API extension to dataset for explicit proxy server host
Henry Minsky
henry.minsky at gmail.com
Fri Jul 13 10:21:51 PDT 2007
On 7/13/07, P T Withington <ptw at openlaszlo.org> wrote:
>
> So the src attribute would still be the real source of the data?
>
> Presumably the proxy needs to vet the requestee and the source being
> requested so that it does not act as an 'open relay'?
There's no really good way I can think of to do that, given that the app
source is readable to a pretty casual observer. Put the proxy should
probably
have a default of "closed", and only speak to specific 3rd party hosts as
configured in a config file.
I wonder if we should have a global proxy config file like [proxy.pac]
> (http://wp.netscape.com/eng/mozilla/2.0/relnotes/demo/proxy-live.html)
>
> On 2007-07-13, at 12:25 EDT, Henry Minsky wrote:
>
> > I recently ran into an issue when trying to deploy a SOLO app to a
> > host
> > which is not running
> > the LPS server. I need to access 3rd party data and images from a
> > server,
> > and due to security
> > policy in Flash and DHTML runtimes, need a proxy server living on
> > the same
> > host that my app is served from.
> >
> > There have been a couple of different PHP HTTP proxies written, and
> > I'd like
> > to add support to our
> > data API to specify an explicit URL for the proxy server. Currently
> > it is
> > implicitly generated using
> > LzBrowser.getBaseURL( ) as the url.
> >
> > I propose adding a "proxyhost" attribute to dataset, which
> > specifies the
> > host to forward requests to.
> > HTTP requests would still be formatted using the existing LZX proxy
> > protocol, so the server to
> > which you point would be expected to look like an LZX server for
> > purposes of
> > requests which are marked
> > as lzt=data or lzt=media. However, it would not be necessary for
> > the proxy
> > server to support all the optional args
> > such as cache control or header forwarding.
> >
> > The syntax would look like this
> >
> > <dataset name="mydata" proxyhost="myproxy.php"/> for a relative url or
> >
> > <dataset name="mydata" proxyhost="/myproxy.php"/> relative to host
> > server
> > root directory
> >
> > <dataset name="mydata" proxyhost="http://myhost.com/proxy/
> > myproxy.php"/>
> > for an absolute url (needs to be
> > on same host as app served from for default security policy of most
> > browsers)
> >
> > Another option would be some global canvas setting
> >
> > <atttribute name="proxyhost" value="/myproxy.php"/>
> >
> > or
> >
> > <canvas proxyhost="/myproxy.php">
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > Henry Minsky
> > Software Architect
> > hminsky at laszlosystems.com
>
>
--
Henry Minsky
Software Architect
hminsky at laszlosystems.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.openlaszlo.org/pipermail/laszlo-dev/attachments/20070713/3b7ac6c7/attachment-0001.html
More information about the Laszlo-dev
mailing list