Thanks, Tim.
I might have found my problem. The data I get while "following TCP stream"
on the manual connection that works correctly is readable.
The data I get while following the stream on the LWP connection is
unreadable... I tried to paste it here but it doesn't paste correctly. I
tried to put on my website for you to see.. but it would display correctly.
If someone can help me out I will attach it to an email for them so they
can see it. Just email me and I will send it to you.
If anyone has any ideas, I appreciate any help.
David Gerler
Gerler Enterprises
PO BOX 16357
Chesapeake VA 23328
http://www.GerlerEnterprises.com/
Nationwide Dial-up from $12.45
http://www.EasySitesForLess.com/
-----Original Message-----
From: tallwine [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 02, 2002 5:12 PM
To: David Gerler
Cc: Sean M. Burke; LWP
Subject: Re: Following link with target="_blank"
In ethereal, after you have captured your packets. Find one of the http
packets and click on it. Then click on the 'Tools' menu and then on
Follow TDP Stream
You should see a readable translation of the http conversation.
-Tim
On Friday, August 2, 2002, at 10:34 AM, David Gerler wrote:
> How do I switch to the "other window" of the browser? I ask because,
> if I
> start a new browser and switch to it. Then enter the uri, it gives me a
> page
> not found. However, if I let it open the new window, the page comes up
> fine.
> I have ethereal installed, I have looked a the capture file but I'm not
> sure
> about what I'm looking for. Any ideas where I can go from here? Ways of
> figuring out how to get to the page I need?
>
> David Gerler
> Gerler Enterprises
> PO BOX 16357
> Chesapeake VA 23328
> http://www.GerlerEnterprises.com/
>
> Nationwide Dial-up from $12.45
> http://www.EasySitesForLess.com/
>
> -----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/
>
>
>