35 ms·
Sounds like in this day and age you can tag everything as either 0 or 9, and leave it to the client to figure it all out. The whole text vs binary reminds me o
by digi_owl 11y ago
Sounds like in this day and age you can tag everything as either 0 or 9, and leave it to the client to figure it all out.
The whole text vs binary reminds me of FTP, and most clients there defaults to requesting everything as binary transfers.
Edit: MIME is no cure-all, i wonder how many times i have seen Firefox get royally confused because the MIME type is wrong.
- ksherlock 11y agoEven if you limit it to text/binary 0/9 you still have problems. 1. your url looks like gopher://dipstick.io/0file or gopher://watchingpaintdry.museum/9folder/file. The filetype is part of the url, but only the client is aware of it -- it's not passed to the server. 2. When using a URL, the client has one idea of the file type but it does not necessarily match what the server thinks the file type is. 2. Error messages. HTTP has a status code to indicate the file doesn't exist (or was moved, etc). Gopher can send the error message back as the payload but... is that in text format or binary format? The server has no idea what format the client expects. Always sending binary data and using out-of-band status codes and file type just keeps life simpler.