Uh oh!
There was an error while loading. Please reload this page.
Helper for parsing headers attributes - #92
Conversation
dg
commented
May 1, 2016
Can you add it? |
@JanTvrdik Is there a standard for this? I haven't looked myself. Shouldn't it be more something like |
JanTvrdik
commented
May 1, 2016
I'll, try to send PR today. |
It depends afaik. There is standard for Accept headers as well as Content-Type header (RFC 7231) at least. |
It's not in one place, but if summarized, it leads to http://search.cpan.org/~ether/HTTP-Message-6.11/lib/HTTP/Headers/Util.pm |
Uf, as it turned out there is no unified standard (as pointed out for example here). So I guess we need to pick a list of headers which we actually want to be able to parse decide based on that. The stuff is so fucked up that even browsers don't implement it correctly http://greenbytes.de/tech/tc/httpcontenttype/ Related links (so I don't have to look for them again)
|
7981e33 to
3fb64f5Compareb9f06ea to
4f6d6c9Compare2ff2f22 to
40175d7Compare9c1fce0 to
96a1c05Comparecaa05a6 to
708b922Compared5b6f20 to
4b8dfd4Compare980b18f to
fe9a87fCompare746cdd5 to
3f62e09Compare
I'm missing a helper for parsing headers, i.e something that turns
attachment; filename="example.php"into[filename => 'example.php']