#1014: AgaviWebRequest HTTP PUT support ignores Content-Type header
---------------------+------------------------------------------------------
Reporter: david | Owner: david
Type: defect | Status: assigned
Priority: normal | Milestone: 0.11.6
Component: request | Version: 0.11.5
Severity: minor | Keywords:
Has_patch: 0 |
---------------------+------------------------------------------------------
Old description:
> It stuffs the PUT data into an {{{AgaviUploadedFile}}} object and blindly
> sets the {{{type}}} to "application/octet-stream". It should instead read
> the {{{Content-Type}}}Â request header, if present, and fall back to
> "text/plain; charset=us-ascii" as defined in
> [[http://tools.ietf.org/html/rfc2045#section-5.2 RFC 2045 section 5.2]]
New description:
It stuffs the PUT data into an {{{AgaviUploadedFile}}} object and blindly
sets the {{{type}}} to "application/octet-stream". It should instead read
the {{{Content-Type}}}Â request header, if present, and then fall back to
"application/octet-stream", as defined in [RFC 1945 (HTTP/1.0) section
7.2.1 http://tools.ietf.org/html/rfc1945#section-7.2.1] and [RFC 2616
(HTTP/1.1) section 7.2.1 http://tools.ietf.org/html/rfc2616#section-7.2.1]
--
Comment(by david):
Sorry, that part about "text/plain; charset=us-ascii" was nonsense. [RFC
1945 (HTTP/1.0) section 7.2.1
http://tools.ietf.org/html/rfc1945#section-7.2.1] and [RFC 2616 (HTTP/1.1)
section 7.2.1 http://tools.ietf.org/html/rfc2616#section-7.2.1] specify
that in case of doubt, the recipient should treat the type of messages as
"application/octet-stream".
--
Ticket URL: <http://trac.agavi.org/ticket/1014#comment:2>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
