[REBOL] Re: read bug?
From: sterling:rebol at: 2-May-2001 14:36
It seems that this thread has wandered from POST to GET problems.
I'll address the issue with GET as best I can.
People see that a long URL used with read:
read http://foo.com/cgi-bin/cgi.r?name=value-of-really-long-data
gets truncated or otherwise fails to read. I ran some tests on my
machine here (Linux w/ Apache) using Core 2.5 on both the client and
CGI end. I made a really big URL of over 7K which looks like the
example above. It made it through just fine.
However, I have seen a truncation of sorts happen in some situations
here though most have been using a browser going to a REBOL CGI
script. Have you tried the same read using a browser?
One possibility is that the receiving system truncates the GET data.
Remember that when using a GET method, all CGI data is passed to the
program on the server using environment variables. If any of the
client browser, webserver, or system env. vars limits the length then
the CGI script on the other end will not get all the data.
So take REBOL out of the picture and see what happens:
#!/usr/bin/perl
print "Content-type: text/html\n\n";
while (($key, $val) = each %ENV) {
print "$key = $val<BR>\n";
}
There's a little perl (yuck) cgi that'll print the env. vars for you.
Try your request with REBOL or a browser against that and see what you
get. Also, with REBOL, turn 'trace/net on' and do the read. What you
see printed to the console is EXACTLY what is being sent into the TCP
port to the server.
Let me know what you find out.
Sterling
