Bruce Weirdan e690e7aac0 Fallback to extension-based content type detection when parsing Content-Type header fails (#13610) ... # Description Previously when nushell failed to parse the content type header, it would emit an error instead of returning the response. Now it will fall back to `text/plain` (which, in turn, will trigger type detection based on file extension). May fix (potentially) nushell/nushell#11927 Refs: https://discord.com/channels/601130461678272522/614593951969574961/1272895236489613366 Supercedes: #13609 # User-Facing Changes It's now possible to fetch content even if the server returns an invalid content type header. Users may need to parse the response manually, but it's still better than not getting the response at all. # Tests + Formatting Added a test for the new behaviour. # After Submitting		2024-08-14 09:47:01 -05:00
..
http	Fallback to extension-based content type detection when parsing Content-Type header fails (#13610)	2024-08-14 09:47:01 -05:00
mod.rs	Add unit tests for HTTP commands. (#8267)	2023-03-02 11:05:18 -08:00
port.rs	Add checks for ports (#11214)	2023-12-03 08:07:15 -06:00