Hi Phillip,
I think you did everything right. I dug through the bug tracker archive and, whenever 
the error happens that you experience, it has turned out to be a PPM / website bug.

Here's what I found, among other articles in the bug tracker bboard. 
http://bugs.activestate.com/ 

Peter Stucki



----------------------------------------

From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Work-around for ppm problem
Date: Mon Nov 27 14:41:41 2000

Full_Name: Daniel Martin
Version: ActivePerl 622
OS: Windows NT 4.0 SP 6a
Submission from: (NULL) (192.88.60.69)


This is in response to bugs 1379 and 1378.

It is arguably a bug on ActiveState's server.  See, ppm uses HTTP to access
ActiveState's machines, and ActiveState's server returns an HTTP response
containing an invalid header; a typical response from ActiveState begins with:
HTTP/1.1 200 OK
Server: Microsoft-IIS/5.0
Date: Mon, 27 Nov 2000 21:58:50 GMT
./NET: text/html
Content-type:text/xml
Content-Length: 9680:

See that ./NET header?  Slashes are explicitly NOT ALLOWED in HTTP header names.
 Once again, we can thank Microsoft for royally lousing up a good protocol by
introducing random variations.  (I assume that ./NET is a Microsoft-introduced
header; if not, then it's ActiveState who fouled up)  This bogus header causes
various bits of ppm to assume that the response starts with the line ./NET.

Anyway, until ActiveState fixes their servers so that they don't send this bogus
header, here's a workaround:
change line 197 of Perl\site\lib\LWP\Protocol\http.pm from
              if ($line =~ /^([a-zA-Z0-9_\-.]+)\s*:\s*(.*)/) {
to
              if ($line =~ /^([a-zA-Z0-9_\/\-.]+)\s*:\s*(.*)/) {

This allows the bogus header to be accepted.

If you do discover who is responsible for this bogus header, please send them a
long angry rant.


--------------------------------------------------------------------------------

Reply 1
Resend

From: Murray Nesbitt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Work-around for ppm problem (APR#1381)
Date: Tue Nov 28 15:09:04 2000

This should be fixed now.  It was a problem with our website.

_______________________________________________
ActivePerl mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/activeperl

Reply via email to