#6 Betsie Times Out

[Anonymous]

I work for an educational institution in the USA.
Whenever I try to use Betsie on any pages on our
web-server, it just times out. The administrator of
that web server says it's because any resource on that
machine requires a cookie, but betsie seems to have
cookie capabilities. The only information that is
stored in the cookie is a approx. 15 alphanumeric
string that is used for identification on our web
server. Is this too advanced for betsie? What else
could be the problem?

[Nobody/Anonymous]

Logged In: NO

Upon further research into our web-server (it's proprietary), I
noticed a comment in a subroutine that says the HTTP
request has to be *EXACTLY* to RFC spec before the
request will be answered... And judging by this comment in
parser.pl:
"# graburl
# homebrewed page grabber thing. gets remote page."

I'm assuming that the requests are being formed in a manner
that the web-server doesn't like so it just ignores them,
therefore causing the request to time out since it never got a
response.. What would it take to get the HTTP requests up
to RFC spec??

[Nobody/Anonymous]

Logged In: NO

OK, I fixed that problem with betsie hanging because of the
mal-formed HTTP requests.. All I had to do was put a \r
before each \n in the HTTP request section.

Now I'm running into a different problem, for some reason
the script isn't getting the cookies and passing them on.
The line that gets the cookies is:

$cookies = $ENV{'HTTP_COOKIE'} || $ENV{'COOKIE'} || "";
Meaning, that if it's not one of the first two, it's blank.
If I change "" to "hi" that gets passed as the cookie. So
for some reason cookies aren't being transferred from the
browser to the script.. I'll keep playing with it and if I
figure anything out, I'll post it here. (If it matters, I'm
using Netscape 6 on linux as my browser.. I'm going to try
it on a windows box as it could just be something with
netscape not liking that request)