Enalmada opened a new issue #1760: ModPagespeedAddResourceHeader Access-Control-Allow-Origin duplicate headers URL: https://github.com/apache/incubator-pagespeed-mod/issues/1760 My server returns proper cors headers for every asset but I noticed that pagespeed optimized assets would not always return the header. I found this [doc ](https://www.modpagespeed.com/doc/configuration#add-resource-header) suggesting I need to use ModPagespeedAddResourceHeader. I added it, cleared my pagespeed cache and everything was fine for a while on production but later people started calling me saying the site was broken and I could see chrome complaining about duplicate Access-Control-Allow-Origin headers on optimized assets. Feeling like an idiot for messing up the flush or something, I flushed again and everything was fine for a while. But I have seen chrome errors pop up again that go away when I add PageSpeed=off. This is a critical issue because chrome refuses to load content with duplicate headers completely destroying the site. I have had to turn it off to stop the random errors but I love pagespeed and want it back. Is it possible to ensure that ModPagespeedAddResourceHeaders feature never duplicates headers? Perhaps it can filter the defined header from incoming responses it is storing, or only adds the header to outgoing response if it is not already there?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
