So are you saying that there is no way for me to use lwp to get these
pages? Sometimes I'm thick... :) I hope I didn't offend anyone with previous
messages.
I am just trying real hard to understand all of this... I don't understand
why I can browse to these pages with IE but I can't do it with perl. Could
it be a protocol change? Do you have any ideas where I might be able to
learn about these problems?
I finally figured out what I was doing wrong with ethereal. I have
intelligible TCP stream on the connection that doesn't work.. This is what I
got:
-----
GET /weborder/default.asp HTTP/1.1
TE: deflate,gzip;q=0.3
Connection: TE, close
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, image/png, */*
Accept-Charset: iso-8859-1,*,utf-8
Accept-Encoding: gzip
Accept-Language: en-US
Host: www.smcorp.com
User-Agent: Mozilla/4.76 [en] (Win98; U)
HTTP/1.0 302 Moved Temporarily
Server: Microsoft-IIS/5.0
Date: Sat, 03 Aug 2002 16:51:58 GMT
Set-Cookie: SITESERVER=ID=68334a10706f97cd66f8fd4b6a82e2b8; expires=Monday,
01-Jan-2035 00:00:00 GMT; path=/; domain=.smcorp.com
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Location: https://www.smcorp.com:443/weborder/welcome_lookup.asp
Content-Length: 175
Content-Type: text/html
Set-Cookie: LoginRedir=; path=/weborder
Cache-Control: private
Age: 0
X-Cache: MISS from sitarala.smcorp.com
Connection: close
<head><title>Object moved</title></head>
<body><h1>Object Moved</h1>This object may be found <a
HREF="https://www.smcorp.com:443/weborder/welcome_lookup.asp";>here</a>.</bod
y>
----------
Could this mean that I'm not accepting redirects with my script?
David Gerler
-----Original Message-----
From: Sean M. Burke [mailto:[EMAIL PROTECTED]]
Sent: Thursday, August 01, 2002 11:42 PM
To: David Gerler; LWP
Subject: RE: Following link with target="_blank"
At 14:53 2002-08-01 -0400, David Gerler wrote:
>The full text of the response: 500 EOF instead of reponse status line
Now that I look at Net::HTTP::Methods, it looks like you're getting that
message because the server is just dropping the socket connection, instead
of giving any sort of proper HTTP reply, even any sort of "No! Go away!"
error reply. The server is just not implementing HTTP right.
--
Sean M. Burke http://www.spinn.net/~sburke/
