[Qgis-developer] proxys, WMS and plugin installer

[Stephan Holl]

Hello Marco, all,

Marco Hugentobler <marco.hugentobler at karto.baug.ethz.ch>, [20090107 -
15:58:16]

> Hi all,
> 
> Thanks for your feedback. I think Borys is right and the plugin
> installer should pick up the proxy type from the settings. Therefore
> I applied the patch in r9939 for testing. 
> 
> I don't have the 'pleasure' to work behind a proxy so I cannot test
> myself. Andreas, Barry, Carson, Stephan, could you test r9939 with
> your proxy configurations at work?

Ok, tests are partly successfull.

I only have success when setting the proxy-type to
HttpCachingProxy. Then the WMS-queries are sending thru our proxy.

Using HttpProxy as Proxytype I have the following entries in my
proxy-logs:

localhost - - [08/Jan/2009 14:55:50] code 501, message
Unsupported method ('CONNECT') 
localhost - - [08/Jan/2009 14:55:50] "CONNECT
212.95.126.11:80 HTTP/1.1" 501 - [08/Jan/2009 14:55:50] queue contains
0 items 
localhost - - [08/Jan/2009 14:55:50] code 501, message Unsupported
method ('CONNECT') 
localhost - - [08/Jan/2009 14:55:50]
"CONNECT 212.95.126.11:80 HTTP/1.1" 501 - [08/Jan/2009 14:55:50] queue
contains 0 items 
localhost - - [08/Jan/2009 14:55:50] code 501, message Unsupported
method ('CONNECT') 
localhost - - [08/Jan/2009 14:55:50]
"CONNECT 212.95.126.11:80 HTTP/1.1" 501 -

If you like to test the proxy-stuff, you could set up InteProxy[1] on
localhost with python InteProxy.py  --workers=1 --debug-level=2
--rewrite-urls --config-file=demo.cfg --port=64609

and set your proxy-entries to localhost:64609 

InteProxy is a proxy to secure OGC-requests between server and client,
but it can also be used as a regular proxy (with some restrictions
though).

Because of sudden absents of the python-bindings I was unable to test
against the plugin installer, sorry :-(

It we had a noproxy-option, everything would be really fun!


Best regards

	Stephan

[1] http://inteproxy.wald.intevation.org

> 
> >But there is also WFS remaining (and what with postgis?)
> 
> True, WFS is using QHttp directly for GetFeature requests and also
> needs to set proxy settings. Also I'm developing an SOS client that
> would also need to do that. It seems reasonable to have a method
> applyProxySettings(QHttp) that can be used by all those classes. For
> postgis there is probably a libpq specific way of proxy setting,
> though I did not check the documentation yet.
> 
> > PS: It would be good to have a noproxy-entry, because some clients
> > complain that they cannot use internal and external WMS in one
> > QGIS-Session.
> 
> Yes, I agree it would be handy to specify a set of urls in option
> dialog for that. Then every URL starting with such a string will not
> use a proxy in its QHttp object (that is a further argument against
> setting proxy at application level).
> 
> Regards,
> Marco 
> 
> 
> 
> Am Mittwoch 07 Januar 2009 07:36:09 schrieb Stephan Holl:
> > Hi Marco,
> >
> > glad that you roled up the proxy-topic again :-)
> >
> > We have several problems with it and I tried to track this down to
> > some point but got lost in QT-stuff. One of my collegues told me
> > that QT uses the CONNECT-method which at least fails on our
> > proxy-server.
> >
> > Apart from that, using QT 4.2.x worked though. I dont have a
> > QT4.2.x-build at hand so I cannot really test against current
> > qgis-trunk.
> >
> > Am Dienstag, 6. Januar 2009 09:48:48 schrieb Marco Hugentobler:
> > > Hi QGIS devs
> > >
> > > I'm a bit lost in the tickets and discussions about proxys. What
> > > is the current state of proxy handling?
> > >
> > > There is patch #1422 that adds the possibility to choose proxy
> > > type for plugin installer (but not WMS). In the ticket it says 'I
> > > have not made any new changes to the plugin installer, as Borys
> > > has already applied the above fix, plus some excellent extras!'.
> > > Does that mean that the patch can be closed?
> > >
> > > I also have a proxy patch (attached) which lets the user select
> > > proxy type and sets it to QgsHttpTransaction (for WMS). I tested
> > > together with Andreas and it seems that setting the proxy and
> > > proxy type at application level does not work. Therefore the
> > > patch sets the proxy configuration to the QHttp object. Do other
> > > proxy users/developers have the same experience? Because I don't
> > > see a reason why the application level proxy does not work.
> > >
> > > Maybe we need a mix of both patches such that proxy works with
> > > WMS and plugin installer?
> > >
> > > Also I think we need a set of proxy testers to try both patches
> > > with different proxy types and report what works/ does not work
> > > with patch #1422 and attached patch. Who would be available?
> >
> > I could give it a go to test. Let me know which revision-number is
> > testable.
> >
> > Best regards
> >
> > 	Stephan
> >
> > PS: It would be good to have a noproxy-entry, because some clients
> > complain that they cannot use internal and external WMS in one
> > QGIS-Session.
> 


-- 
Stephan Holl <stephan.holl at intevation.de> | Tel.: +49 (0)541-33 508 3663
Intevation GmbH, Neuer Graben 17, 49074 OS  |  AG Osnabrück - HR B 18998
Geschäftsführer:  Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 206 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/qgis-developer/attachments/20090108/2f3d9398/signature.bin