https://bz.apache.org/bugzilla/show_bug.cgi?id=51223
--- Comment #24 from oberhamsi <[email protected]> --- Thank you for pointing me to that bug. Our issues is with 304s generated by Apache in response to disk files. The discussion in 61820 seems to differentiate between responses generated by e.g. CGI and responses genereated by apache itself. I don't understand why. I get that some kind of filtering makes sense to adhere strictly to the spec but the CORS headers do not describe the content ("representation metadata") so i assumed they could be let through. As a workaround to 304 having no CORS information, we attach a query parameter ?origin=document.location.origin to all CORS requests which are potentially served to multiple domains. This forces the browsers to have seperate cache entries for each origin. If we don't do this, the arising bugs are surprising to newcomers and difficult to debug since the behaviour depends on local cache. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
