Hello,

Thank you for the response. I agree, HTTP is not HTTPS and I had not thought to try this. But changing this line of code only serves to confuse Perl about where the proxy is located. The proxy no longer sees any traffic and the script just hangs without doing anything. I haven't confirmed this with a packet sniffer, but I'd guess that this change directs all outgoing HTTPS traffic to port 443 of the proxy machine, rather than port 8118 where it should go.

I should point out that I need both HTTP and HTTPS to go through the proxy. I can think of very few sites that are purely HTTPS. Yahoo, for instance, would use HTTPS for authentication and then move back to HTTP for most other pages.

I think that CONNECT needs to be implemented in HTTP::Request, then WWW::Mechanize needs to test if a proxy is defined and if it's for HTTPS, then call CONNECT rather than GET. I just wish I knew that this was the right thing to do before I modify these packages...

Thanks again for your suggestion.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.