This is preventing the webapp I'm trying to create from being able to read back the ipfs-hash header whenever a file is posted.
The only work around that I can think of is to require that the webapp be run directly out of the IPFS filesystem of the public writable IPFS gateway that is being used to post the files.
For development looks like I'm going to have to add a localhost proxy....
What a pain in the ass!
It would be better to be able to randomly select from a list of writable gateways instead of the way things are starting to become painful...