jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Mouawad <p.moua...@ubik-ingenierie.com>
Subject Re: Bug 60190 - Content-Type is added for POST unconditionally
Date Wed, 11 Oct 2017 18:45:09 GMT
Hello
Any feedback on this ?
Thanks

On Fri, Sep 8, 2017 at 2:12 PM, Philippe Mouawad <
p.mouawad@ubik-ingenierie.com> wrote:

> Hello,
> How about not adding this anymore if not set and having a property that
> allows to do that ?
>
>    - post_add_content_type_if_missing=false
>
>
> What is the risk ?
>
> As per:
>
>    - https://www.w3.org/Protocols/rfc2616/rfc2616-sec7.html
>
> Any HTTP/1.1 message containing an entity-body SHOULD include a
> Content-Type header field defining the media type of that body. If and only
> if the media type is not given by a Content-Type field, the recipient MAY
> attempt to guess the media type via inspection of its content and/or the
> name extension(s) of the URI used to identify the resource. If the media
> type remains unknown, the recipient SHOULD treat it as type
> "application/octet-stream".
>
>
> --
> Regards.
> Philippe
>
>
>


-- 
Cordialement.
Philippe Mouawad.
Ubik-Ingénierie

UBIK LOAD PACK Web Site <http://www.ubikloadpack.com/>

UBIK LOAD PACK on TWITTER <https://twitter.com/ubikloadpack>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message