Open chesty opened 9 months ago
ug. after more testing I still get the warning after setting an expires header.
I think it's just how firefox works. There's no bug or anything. I guess I'll leave it open in case you want to add an expires header anyway, if not, please close.
What I see when I get this issue is some parts of the map tiles are not downloaded and rendered. But the same error is shown in Chrome.
From my understanding, this warning doesn't cause any issues other than it looks like an error when watching requests in the network tab of the firefox web developer tools.
The warning can be squelched by setting an expires header, which I've done in nginx, but I thought I would create an issue in case you wanted to add a maxAge option in the node app. Maybe setting an expires header is a good thing in general besides the ugly firefox warning.
https://stackoverflow.com/questions/704561/ns-binding-aborted-shown-in-firefox-with-httpfox
Thanks for your work. Appreciate it.