OpenEuphoria

Re: CGI and euc

• Posted by useless_ Jan 14, 2013
• 2373 views

According to me and O'Reilly, the CGI script is perfectly within it's limits to make a complete HTTP header to send to the httpd. Technically, HTTP/1.0 is obsolete, and yet people still use it. And while i am mentioning O'Reilly, here's a quote from one of his books:

print "$server_protocol 200 OK", "\n"; 
print "Server: $server_software", "\n"; 
print "Content-type: text/plain", "\n\n"; 
print "OK, Here I go. I am going to count from 1 to 50!", "\n"; 

Note the lack of \r at the end of header lines or between the header and the body. This is why i say Euphoria should be adaptive or smart when parsing headers, and not enforce the rules du jour. Basically, whatever the first line ends with, that's what you are going to get as a line/header terminator, and i don't care if it's "right" or not, it's what is.

Any number of spaces, even, from RFC2616: "The field value MAY be preceded by any amount of LWS, though a single SP is preferred.". Use only one to make CoBaJo happy.

This site uses Transitional, so does my site. If the page is compliant to what's stated, and you simply change that header, your page is likely not compliant to HTML5 and will display wrong.

I have links such as

<a href="canoe pontoons.html"> 

and they work fine. The browser handles it. It's not illegal to have spaces until the space is actually sent to the server to get a page or post data. As general good programmng style, you should encode just prior to sending, as a single point in the program, for everything (not in the page body) being sent, else you could have a program flow bug where the url gets encoded twice. I've seen it happen.

And by the way, i also will object to http.e transparently following redirects, perhaps i don't want to goto the new url, the programmer should see the redirect and decide yes/no to send the new url to http.e for a second fetch.

useless

Not Categorized, Please Help