Bug 1830022 Comment 7 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Hey Martin,

There are couple of issues before we land this. 
Do you think it is OK to treat IDK header as CORS-safe, i.e. can we use this header in fetch API's `no-cors` mode. Currently we treat the [following](https://searchfox.org/mozilla-central/source/dom/base/nsContentUtils.cpp#7863-7879) headers as CORS-safe

I just noticed that the [draft](https://datatracker.ietf.org/doc/draft-ietf-httpapi-idempotency-key-header/) has expired. Do we have any reasons not to land this patch?

Kindly confirm.

Thanks
Revision 1 by
on 
Hey Martin,

There are couple of issues before we land this. 
Do you think it is OK to treat IDK header as CORS-safe, i.e. can we use this header in fetch API's `no-cors` mode. Currently we treat the [following](https://searchfox.org/mozilla-central/rev/f79a574afca9aad0b851fc59b27cf80ea09c0e0c/dom/base/nsContentUtils.cpp#7856-7872) headers as CORS-safe

I just noticed that the [draft](https://datatracker.ietf.org/doc/draft-ietf-httpapi-idempotency-key-header/) has expired. Do we have any reasons not to land this patch?

Kindly confirm.

Thanks

Back to Bug 1830022 Comment 7