Well your requested URL looks okay to me, but how do you know you aren't hitting a redirect, and it's some subsequent URL that's causing you grief?

A simple check to see whether this is the case would look something like (tested):

#! /usr/bin/perl -w

use strict;
use LWP::UserAgent;
use HTTP::Request;

my $ua = LWP::UserAgent->new;
my $res = $ua->simple_request( HTTP::Request->new('GET', shift ));

print $res->status_line, "\n";

[download]

If you get a 300, 301 or 302 you're being redirected, so you'll have to look farther afield. If, as it appears in your comments, you are using SOAP, why don't you take a look at the SOAP hierarchy on CPAN?


print@_{sort keys %_},$/if%_=split//,'= & *a?b:e\f/h^h!j+n,o@o;r$s-t%t#u'

In reply to Re: Cannot determine protocol by grinder
in thread Cannot determine protocol by lablett

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.