CSP now uses a different header for sending reports. This is already in Chrome stable.

CommentFileSizeAuthor
#8 seckit-2200187-8.patch2.54 KBmilodesc
#1 seckit-2200187-1.patch791 bytestwistor

Comments

twistor’s picture

twistor commented
Status: Active » Needs review
StatusFileSize
new seckit-2200187-1.patch791 bytes

Here's the change.

https://dvcs.w3.org/hg/content-security-policy/rev/9c1ebbb88a76

  • Commit d994c71 on 7.x-1.x authored by twistor, committed by jweowu: 
    Issue #2200187 by twistor: Report header has changed.
jweowu’s picture

jweowu commented
Title: Report header has changed. » CSP report Content-Type has changed.
jweowu’s picture

jweowu commented
Status: Needs review » Fixed

Improved the Content-Type detection in commit fa6dbe3af027f00f701e712c3797d0632800983d.

jweowu’s picture

jweowu commented

Included in 7.x-1.9-rc1.

Please follow #2200671: 7.x-1.9 release candidate to track any additional release candidates prior to the stable release.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

  • Commit d994c71 on 7.x-1.x, 8.x-1.x authored by twistor, committed by jweowu: 
    Issue #2200187 by twistor: Report header has changed.
milodesc’s picture

milodesc
he/him
commented
StatusFileSize
new seckit-2200187-8.patch2.54 KB

The attached patch is working for me on 6.x-1.7.

jweowu’s picture

jweowu commented

Thanks milodesc. I've committed and pushed that to 6.x-1.x, given your report, and as I can see it makes the function the same as in 7.x-1.x.

FWIW if you're willing to roll and test patches for 6.x-1.x, I'm happy to commit them (particularly if it's obviously in line with the 7.x branch). I haven't attempted to maintain the 6.x branch to date (and don't wish to dedicate significant time to that); but if you wish to get an official -dev release (at minimum) which is more up to date, I'll support you in that.