X-Content-Type-Options

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

X-Content-Type-Options

Anne van Kesteren
Header field name: X-Content-Type-Options

Applicable protocol: http

Status: standard

Author/Change controller: WHATWG

Specification document(s):
https://fetch.spec.whatwg.org/#x-content-type-options-header

Related information: N/A


--
https://annevankesteren.nl/

_______________________________________________
Ietf-message-headers mailing list
[hidden email]
https://www.ietf.org/mailman/listinfo/ietf-message-headers
Reply | Threaded
Open this post in threaded view
|

Re: X-Content-Type-Options

Ted Hardie-2
Hi Anne,

https://tools.ietf.org/html/rfc6648 suggests avoiding the x- construct wherever possible.  Is it possible to go to Content-Type-Options, without the X-?

regards,

Ted Hardie

On Mon, May 15, 2017 at 3:40 AM, Anne van Kesteren <[hidden email]> wrote:
Header field name: X-Content-Type-Options

Applicable protocol: http

Status: standard

Author/Change controller: WHATWG

Specification document(s):
https://fetch.spec.whatwg.org/#x-content-type-options-header

Related information: N/A


--
https://annevankesteren.nl/

_______________________________________________
Ietf-message-headers mailing list
[hidden email]
https://www.ietf.org/mailman/listinfo/ietf-message-headers


_______________________________________________
Ietf-message-headers mailing list
[hidden email]
https://www.ietf.org/mailman/listinfo/ietf-message-headers
Reply | Threaded
Open this post in threaded view
|

Re: X-Content-Type-Options

Mark Nottingham
It's already widely-deployed, so it's grandfathered in, I think.

https://msdn.microsoft.com/library/gg622941(v=vs.85).aspx


> On 18 May 2017, at 4:56 am, Ted Hardie <[hidden email]> wrote:
>
> Hi Anne,
>
> https://tools.ietf.org/html/rfc6648 suggests avoiding the x- construct wherever possible.  Is it possible to go to Content-Type-Options, without the X-?
>
> regards,
>
> Ted Hardie
>
> On Mon, May 15, 2017 at 3:40 AM, Anne van Kesteren <[hidden email]> wrote:
> Header field name: X-Content-Type-Options
>
> Applicable protocol: http
>
> Status: standard
>
> Author/Change controller: WHATWG
>
> Specification document(s):
> https://fetch.spec.whatwg.org/#x-content-type-options-header
>
> Related information: N/A
>
>
> --
> https://annevankesteren.nl/
>
> _______________________________________________
> Ietf-message-headers mailing list
> [hidden email]
> https://www.ietf.org/mailman/listinfo/ietf-message-headers
>
> _______________________________________________
> Ietf-message-headers mailing list
> [hidden email]
> https://www.ietf.org/mailman/listinfo/ietf-message-headers

--
Mark Nottingham   https://www.mnot.net/

_______________________________________________
Ietf-message-headers mailing list
[hidden email]
https://www.ietf.org/mailman/listinfo/ietf-message-headers
Reply | Threaded
Open this post in threaded view
|

Re: X-Content-Type-Options

Anne van Kesteren
On Thu, May 18, 2017 at 3:55 AM, Mark Nottingham <[hidden email]> wrote:
> It's already widely-deployed, so it's grandfathered in, I think.
>
> https://msdn.microsoft.com/library/gg622941(v=vs.85).aspx

That is exactly it. I think everyone knows better now, so I wouldn't
expect much more of these, but it's also not worth the effort of
trying to get rid of the prefix and adding all the complexity of
supporting two headers meanwhile.


--
https://annevankesteren.nl/

_______________________________________________
Ietf-message-headers mailing list
[hidden email]
https://www.ietf.org/mailman/listinfo/ietf-message-headers
Reply | Threaded
Open this post in threaded view
|

Re: X-Content-Type-Options

Anne van Kesteren
In reply to this post by Anne van Kesteren
On Mon, May 15, 2017 at 9:40 AM, Anne van Kesteren <[hidden email]> wrote:

> Header field name: X-Content-Type-Options
>
> Applicable protocol: http
>
> Status: standard
>
> Author/Change controller: WHATWG
>
> Specification document(s):
> https://fetch.spec.whatwg.org/#x-content-type-options-header
>
> Related information: N/A

I forwarded this to IANA ([IANA #971687]) on July 21, but it hasn't
been processed yet as far as I can tell. Is that normal?


--
https://annevankesteren.nl/

_______________________________________________
Ietf-message-headers mailing list
[hidden email]
https://www.ietf.org/mailman/listinfo/ietf-message-headers
Reply | Threaded
Open this post in threaded view
|

Re: X-Content-Type-Options

Alexey Melnikov
On 07/08/2017 11:29, Anne van Kesteren wrote:

> On Mon, May 15, 2017 at 9:40 AM, Anne van Kesteren <[hidden email]> wrote:
>> Header field name: X-Content-Type-Options
>>
>> Applicable protocol: http
>>
>> Status: standard
>>
>> Author/Change controller: WHATWG
>>
>> Specification document(s):
>> https://fetch.spec.whatwg.org/#x-content-type-options-header
>>
>> Related information: N/A
> I forwarded this to IANA ([IANA #971687]) on July 21, but it hasn't
> been processed yet as far as I can tell. Is that normal?
Hi Anne,
The registry is Expert Review, so it needs to be reviewed by designated
expert (Graham Klyne). So most likely IANA is waiting for him. But I can
chase that.

Best Regards,
Alexey

_______________________________________________
Ietf-message-headers mailing list
[hidden email]
https://www.ietf.org/mailman/listinfo/ietf-message-headers