Re: CGI and euc

new topic     » goto parent     » topic index » view thread      » older message » newer message
CoJaBo2 said...
useless_ said...

I wasn't discussing browsers, i was discussing a Eu CGI app sending urls in plain un-escaped text to anything. My Eu code can read plain text in webpages and decide to follow or not, escape or not, and my choices of browsers behave well also. I am not changing anything to suit you.

This thread is not about your app; it is about bugmagnet's app, which outputs HTML. In HTML, browser or no browser, links have to be escaped.


I wasn't trying to help with my app, i was bugmagnet's app. But my app runs fine in contradiction to how you say it should be. HTML is plain text with SGML tags, i've used SGML before Win3 came out. The browser, or bugmagnet's app, should accept the plain text, and make it compliant to what the httpd is expecting before it is sent to the server. But the plain text, as recieved in the body of the HTML, need not be pre-encoded by the httpd. If you type in an url with spaces in it to a browser, or to an Eu app, it's THEN the browser or the Eu app's job to encode it before sending it. Same with the urls in the webpage body.

useless

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu