Databases
StackOverflow2013
Postsdbo
POPerl LWP::UserAgent request does not return using http1.1 but working fine using http1.0!? Why?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPerl LWP::UserAgent request does not return using http1.1 but working fine using http1.0!? Why?
    primarykey
    data
    text
    <p>I have a very simple script (on a SLES11 system) to send a http1.1 request to a server. This worked fine for a long time. Since a couple of days it stopped working. I have no idea why. After some investigation I found out forcing the script to use http1.0 it is working again. I have no idea why. And I want to know why it is not working in its default http1.1 mode.</p> <p>I already enabled debugging as much as I know it (see code below). But I do not see anything - my script just hangs. There is no network activity. I neiter see that a socket will be openend (netstat -a), nor I see any incoming traffic form my client on the server. (A "telnet myserver myport" works fine.)</p> <p>Can someone please help me how to track down this problem? How can I enable more debug to see where the real problem is?</p> <pre><code>#!/usr/bin/perl -w use strict; use warnings; use Data::Dumper; use HTTP::Request::Common; use LWP::Debug qw(+); use LWP::UserAgent; # Workaround: forcing http1.0 instead of using http1.1, it works again! use LWP::Protocol::https10 (); LWP::Protocol::implementor('https', 'LWP::Protocol::https10'); # EO workaround my $ua = LWP::UserAgent-&gt;new; $ua-&gt;ssl_opts( verify_hostname =&gt; 0 ); my $response = $ua-&gt;request( POST 'https://myuser:mypassword@myserver:8888/service/myservice', Connection =&gt; 'close', # Edit: added, see comments below Content_Type =&gt; 'text/xml', Content =&gt; '... my content ...' ); </code></pre> <p>$ua->request() does not return! I need to kill/^C the script!</p> <p>Edit: ok, no one seems to have an idea how to continue. So I startet debugging it using perl debugger.</p> <pre><code>LWP::UserAgent::post(/usr/lib/perl5/site_perl/5.10.0/LWP/UserAgent.pm:418): 418: return $self-&gt;request( HTTP::Request::Common::POST( @parameters ), @suff ); </code></pre> <p>So I can see it is not returning from request().</p> <p>Anyway, due to the fact that <code>LWP::UserAgent</code> calls <code>HTTP::Request::Common</code> I changed my example code above back to use <code>HTTP::Request::Common</code> to skip that step while debugging.</p> <p>Ok... New result:</p> <pre><code>LWP::Protocol::implementor(/usr/lib/perl5/site_perl/5.10.0/Net/HTTPS.pm:26): 26: eval { require IO::Socket::SSL; }; </code></pre> <p>Inside request() it hangs at <code>IO::Socket::SSL</code>. Means, this <em>script</em> it enough for further debug:</p> <pre><code>#!/usr/bin/perl require IO::Socket::SSL; </code></pre> <p>This statement does not come back.</p> <p>Further down, inside <code>IO::Socket::SSL</code> it hangs at:</p> <pre><code>IO::Socket::SSL::CODE(0x1274370)(/usr/lib/perl5/site_perl/5.10.0/IO/Socket/SSL.pm:92): 92: Net::SSLeay::SSLeay_add_ssl_algorithms(); </code></pre> <p>Ahhhh! There is already a bugreport concerning this issue: <a href="https://rt.cpan.org/Public/Bug/Display.html?id=83890" rel="nofollow">Net-SSLeay hangs on Suse 11 P2</a> pointing to <a href="https://rt.cpan.org/Public/Bug/Display.html?id=81575" rel="nofollow">Bug #81575</a> that says:</p> <blockquote> <p>I enountered this same issue on SLES 11 SP2, which has openssl-0.9.8j installed. An upgrade to openssl-0.9.8r did resolve the problem. ... The packages for 0.9.8r can be found in this repository: <a href="http://download.opensuse.org/repositories/security:/fips/" rel="nofollow">http://download.opensuse.org/repositories/security:/fips/</a></p> </blockquote> <p>Guess that's it!</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USEnkidu
    1. USEnkidu
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPerl LWP::UserAgent request does not return using http1.1 but working fine using http1.0!? Why?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPerl LWP::UserAgent request does not return using http1.1 but working fine using http1.0!? Why?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAre you getting any errors? Bareword `POST` should get some errors I would think. Also, why not just use the `post()` method in `LWP::UserAgent`?
      singulars
      1. POPerl LWP::UserAgent request does not return using http1.1 but working fine using http1.0!? Why?
      1. USchrsblck
    2. CONo, I do not get any output. Nothing. It just hangs. Well, I just stripped down the script to these few lines. Of course I directly could use LWP::UserAgent but it has exaclty the same behaviour...
      singulars
      1. POPerl LWP::UserAgent request does not return using http1.1 but working fine using http1.0!? Why?
      1. USEnkidu
    3. COYou are using `LWP::UserAgent`. I am curious why you're not using the `post()` method. And I'm curious about the `POST` Bareword, why doesn't this error out? What happens if you change that line to `$ua->post($url, Content_Type => 'text/xml', Content => $content, );`
      singulars
      1. POPerl LWP::UserAgent request does not return using http1.1 but working fine using http1.0!? Why?
      1. USchrsblck
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload