In comp.lang.perl.misc, mike <mikaelpetter...@hotmail.com> wrote:
> The script I have below is used o access an internal website with https
> (so no proxy here).
Yet this looks like a proxy error.
> $ua->no_proxy("<internalsite>.se");
> my $url = "http://<internalsite>.se/org.testng.eclipse/site.xml";
^^^^^^^ ^^^^^
Hmmm. No https there. And no port specified.
> LWP::UserAgent::request: Simple response: Found
Ahh, a redir.
> LWP::UserAgent::send_request: GET
> https://<internalsite>.se/org.testng.eclipse/site.xml
> LWP::UserAgent::_need_proxy: Not proxied
> LWP::Protocol::http::request: ()
> LWP::UserAgent::request: Simple response: Internal Server Error
> Error: 500 Can't connect to <internalsite>.se/:443 (Bad service '8080/')
^^^^^^^^
At this point I'm really curious why the ":443" appears after the "/",
which would imply a port 80 http request for a resource named "/:443".
Which perhaps that server is then trying something and giving the
error you see?
Myself, I'd try to duplicate this with other tools at this point, in
particular non-browsers, in case there is some browser header sniffing
affecting this.
Elijah
------
or check logs on <internalsite>.seif you have access to those
> In comp.lang.perl.misc, mike <mikaelpetter...@hotmail.com> wrote:
> > The script I have below is used o access an internal website with https
> > (so no proxy here).
> Yet this looks like a proxy error.
> > $ua->no_proxy("<internalsite>.se");
> > my $url = "http://<internalsite>.se/org.testng.eclipse/site.xml";
> ^^^^^^^ ^^^^^
> Hmmm. No https there. And no port specified.
> > LWP::UserAgent::request: Simple response: Found
> Ahh, a redir.
> > LWP::UserAgent::send_request: GET
> > https://<internalsite>.se/org.testng.eclipse/site.xml
> > LWP::UserAgent::_need_proxy: Not proxied
> > LWP::Protocol::http::request: ()
> > LWP::UserAgent::request: Simple response: Internal Server Error
> > Error: 500 Can't connect to <internalsite>.se/:443 (Bad service '8080/')
> ^^^^^^^^
> At this point I'm really curious why the ":443" appears after the "/",
> which would imply a port 80 http request for a resource named "/:443".
> Which perhaps that server is then trying something and giving the
> error you see?
> Myself, I'd try to duplicate this with other tools at this point, in
> particular non-browsers, in case there is some browser header sniffing
> affecting this.
It may also be worth tracking the connection with tcpdump or wireshark
or something similar, or just using the lwp-request tool with the
-uUsSeE options. I suspect what's happening is that internalsite.se is
sending a malformed redirect response.