[Wellington-pm] Problems with HTTPS through LWP.

[Srdjan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Unfortunately I will be leaving soon so I cannot help you a lot.
"Can't read entity body" I have never seen (I believe, but I'm getting old...),
but...
"Internal server error" I've seen a lot when trying to talk to an IIS server.
But it did translate to timeout. There's something about IIS and SSLeay. I know
that guys with IIS had to (reluctantly) change something on their end, and their
mumble was "Well it works with php", and php uses curl.

michael at diaspora.gen.nz wrote:
> Srdjan writes:
>> I'm out for lunch, but what's the aoutput of respone->as_string? 500 is client
>> assigned code, ie not the response from server.
>> I bet it's a timeout...
> 
> Nope.  As I said, it's a failed read call, returning undef rather than 0.
> 
> To be more exact, LWP::Protocol::collect seems to execute 1 read
> (as a call to Net::HTTP::Methods::my_read, via read_entity_body in
> the same package) that returns 4096 bytes; another that returns 375
> bytes; and then a third, which returns undef, which in turn causes
> LWP::Protocol::http::request in the anonymous function passed to collect
> to, well, die.
> 
> What should be returned is 0 (indicating EOF), which seems to happen in
> cases that I haven't tracked down yet.
> 
> The 500 is either 'Can't read entity body', or 'Internal server error'.
> Seems to vary.
> 
> Bizarre, eh?
> 
> (Thanks for reading the email -- it seemed a little bit dense as I was
> writing it...)
> 
>     -- michael.
> _______________________________________________
> Wellington-pm mailing list
> Wellington-pm at pm.org
> http://mail.pm.org/mailman/listinfo/wellington-pm
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEl1FKZtcHxCitRpgRAjx+AKDMOhE2b6hD+HwA1/eSYmDrorvWDACgq/K8
iwliWWpgfgVr+/EcR+hGXvo=
=1zjb
-----END PGP SIGNATURE-----