in reply to Re: Problems with IO::Socket::INET
in thread Problems with IO::Socket::INET
Thank you very much for your help. I suspected it was something with the fact that I was using print, but not that it was multiple print statements since the 'rest' of the request was contained in one packet (or so it seems, looking at ethereal output). At any rate, if I construct a single string and send that as a single print, it behaves the same way through ethereal. Now, I am getting a different error from the Linksys, but I suspect that is a different issue.
As for the carriage returns, I was only using \r\n because that is what the examples I worked from used and the ethereal output from wget confirmed. I am working on Linux and have no current plans to port this to any other platforms, but you have piqued my interest. When I use \015\012 in place of the \r\n in my string, I get exactly the same results when looking at the packet....even the mysterious missing \r after the base64 encoded string.
Off for more testing. Thanks again for your help.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^3: Problems with IO::Socket::INET
by scottknight (Novice) on Nov 29, 2004 at 23:39 UTC |