service workers confused by container headers on soundcloud.com

[zesty]

proxying soundclound.com to burpsuite

the service workers (I think?) send different requests (OPTIONS instead of GET) to the cdn (and they get 403'd) when the option to "Add container header" is enabled; works fine when disabled

the result is that the page doesn't load right and testing isn't possible

I'll add more info if anyone seems to be monitoring what seems to be an abandoned project...

[zesty]

ns_error_interception_failed