Skip Menu |

This queue is for tickets about the HTTP-Proxy CPAN distribution.

Report information
The Basics
Id: 77092
Status: resolved
Priority: 0/
Queue: HTTP-Proxy

People
Owner: Nobody in particular
Requestors: dvadell [...] clustering.com.ar
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Unable to upload attachment to gmail
Date: Wed, 9 May 2012 14:25:55 -0300
To: bug-HTTP-Proxy [...] rt.cpan.org
From: "Diego M. Vadell" <dvadell [...] clustering.com.ar>

Message body is not shown because it is too large.

Message body is not shown because it is too large.

Subject: Re: [rt.cpan.org #77092] Unable to upload attachment to gmail
Date: Wed, 9 May 2012 22:10:45 +0200
To: "Diego M. Vadell via RT" <bug-HTTP-Proxy [...] rt.cpan.org>
From: "Philippe Bruhat (BooK)" <book [...] cpan.org>
On Wed, May 09, 2012 at 01:26:15PM -0400, Diego M. Vadell via RT wrote: Show quoted text
> > First of all, thanks for HTTP::Proxy. I'm trying to index my own navigation > and with it's filters, it was very easy.
Thanks for the kind words. I'd be interested in seeing this script, as it seems an interesting tool to have. Simon Cozens told me that he had a similar tool (called wherewas) based on HTTP::Proxy, which basically gave him a search engine for anything he browsed, thus allowing him to easily find the URL to a page that he vaguely remembered. Show quoted text
> The only problem I'm having is that > I cannot send an attachment via gmail. The attachment progress bar gets > stuck, no matter how much time I let it load. I tried with a 90Kbytes > attachment. Also, if I disable the proxy, it works instantly. > > So I tried with my webmail (Egroupware 1.6) and the same happened. Even > with big emails like this one, I have to disable the proxy just to send. > Everything else works flawlessly. > > Also, if I compose a tiny message ( just a couple of lines ) I can send it > using the proxy.
Show quoted text
> Some information:
Thanks for the log. I see your problematic traffic goes through a CONNECT method. CONNECT support in HTTP::Proxy is not very good, to say the least. In my understanding, you're connecting to Gmail using https, so the simplest way to avoid going through your HTTP::Proxy for https traffic (since HTTP::Proxy is not able to peek into it anyway, you probably do not care). So simply disable the proxy on https traffic in your browser, and you should be able to use https sites correctly. For a few years now, I've been thinking of a rewrite of HTTP::Proxy that would focus on the content (HTTP messages) and not on the protocols (HTTP, TCP and SSL, which are better handled by the appropriate programs). With Plack, this seems very possible, but I'm lacking time, so don't hold you breath. :-S -- Philippe Bruhat (BooK) The worst curses in the world are boils, pestilence and having partners (not necessarily in that order). (Moral from Groo The Wanderer #6 (Pacific))
Subject: Re: [rt.cpan.org #77092] Unable to upload attachment to gmail
Date: Wed, 9 May 2012 17:17:52 -0300
To: bug-HTTP-Proxy [...] rt.cpan.org
From: "Diego M. Vadell" <dvadell [...] clustering.com.ar>
Hi Philippe, Thanks for your answer. The script is still a first try, and it is very raw. But if you send me your address I will email you with more details. I will apply the workarround you told me. Nevertheless, I find it very useful. Cheers -- Diego Show quoted text
----------------original message----------------- From: "Philippe 'BooK' Bruhat via RT" bug-HTTP-Proxy@rt.cpan.org To: dvadell@clustering.com.ar Date: Wed, 9 May 2012 16:11:04 -0400 -------------------------------------------------
> > > On Wed, May 09, 2012 at 01:26:15PM -0400, Diego M. Vadell via RT wrote:
>> >> First of all, thanks for HTTP::Proxy. I'm trying to index my own
navigation
>> and with it's filters, it was very easy.
> > Thanks for the kind words. > > I'd be interested in seeing this script, as it seems an interesting > tool to have. Simon Cozens told me that he had a similar tool (called > wherewas) based on HTTP::Proxy, which basically gave him a search engine > for anything he browsed, thus allowing him to easily find the URL to a > page that he vaguely remembered. >
>> The only problem I'm having is that >> I cannot send an attachment via gmail. The attachment progress bar gets >> stuck, no matter how much time I let it load. I tried with a 90Kbytes >> attachment. Also, if I disable the proxy, it works instantly. >> >> So I tried with my webmail (Egroupware 1.6) and the same happened. Even >> with big emails like this one, I have to disable the proxy just to send. >> Everything else works flawlessly. >> >> Also, if I compose a tiny message ( just a couple of lines ) I can send
it
>> using the proxy.
>
>> Some information:
> > Thanks for the log. I see your problematic traffic goes through a > CONNECT method. CONNECT support in HTTP::Proxy is not very good, > to say the least. > > In my understanding, you're connecting to Gmail using https, > so the simplest way to avoid going through your HTTP::Proxy > for https traffic (since HTTP::Proxy is not able to peek into > it anyway, you probably do not care). > > So simply disable the proxy on https traffic in your browser, > and you should be able to use https sites correctly. > > For a few years now, I've been thinking of a rewrite of HTTP::Proxy > that would focus on the content (HTTP messages) and not on the protocols > (HTTP, TCP and SSL, which are better handled by the appropriate programs). > With Plack, this seems very possible, but I'm lacking time, so don't hold > you breath. :-S > > -- > Philippe Bruhat (BooK) > > The worst curses in the world are boils, pestilence and having partners > (not necessarily in that order). (Moral from Groo The Wanderer #6
(Pacific))
> > >
On Wed May 09 16:18:02 2012, dvadell@clustering.com.ar wrote: Show quoted text
> Hi Philippe, > > Thanks for your answer. The script is still a first try, and it is very > raw. But if you send me your address I will email you with more details. >
You'll be interested to know that I have applied the changes proposed in this ticket https://rt.cpan.org/Ticket/Display.html?id=90414 which should improve how HTTP::Proxy handles https. Let me know if that works for you. -- BooK