3 ms·
in the mid 90s i worked in a machine shop that had a side business where they had catalogs. They were trying to send .TIFF files over 14.4 or 28.8 modems. TIFF
by genewitch 3y ago
in the mid 90s i worked in a machine shop that had a side business where they had catalogs. They were trying to send .TIFF files over 14.4 or 28.8 modems. TIFF files over 10MB, so no floppy (easily.) No CD-R, Jazz/zip.
These days in the same circumstance as you (and they) had, i'd fedex them a USB stick, or optical disc, depending. Because the first time someone said "the web page you linked is just displaying garbage" i'd turn in my tech credentials, because that's probably my server's fault, not the browser. MIME has been a thing for three decades, at least. it sounds like someone tried to use a static html daemon to share a zip file, and it assumes everything is ascii. like it's 19xx and zmodem hasn't been invented yet.
- Filligree 3y agoAs was pointed out in a cousin comment, it's not necessarily the browser or the webserver configuration. SSL proxies -- corporate middleware -- have a habit of breaking this way, by stripping the content-disposition field or similar.
- treadmill 3y agoLet the user talk to their IT department and have them reconfigure their snake oil so it's not broken?
- cxr 3y agoIt would have to be mangling both the Content-Disposition and Content-Type headers. If that's really happening (I have my doubts) and that's a client you want to continue supporting, then the next step would be limiting yourself to SingleFileZ-style ZIP payloads that can be as text/html.