Add ability to include cookie headers in imagery requests

[cigazze]

Strava has recently made a change to their global heatmap tiles that (as of now) requires certain cookies to be provided as part of the Cookie header, instead of query params. This is currently impossible with JOSM.

Some way to provide cookies for JOSM to include in an imagery source's requests would help solve this issue.

[stoecker]

RTFM: Maps:
custom-http-header - HTTP headers to be sent to server (replacement of {header(header, value)}). It has two attributes header-name and header-value. Might be specified multiple times.

[cigazze]

That seems to specifically apply to the XML at josm.openstreetmap.de/maps, not imagery sources added manually through the UI. There's not currently any way to do this with the UI, and it's not documented how to add these cookies manually (to the preferences.xml or wherever else this is supposed to be done.) The remote XML isn't really relevant here since these are authentication cookies that are user-specific and refresh regularly.

[stoecker]

Again: Read before writing: Maps. Especially sentence 2: The URL can be customized in the advanced preferences (key imagery.layers.sites). Using multiple sources at the same time is possible.

If you have special requirements, then you must use the XML format to supply the information (can be a local file). There will be no interface for that stuff.

[cigazze]

I read that. The detail that you can put in the path a local file there is not documented, nor included in the section that you linked, and I would never have guessed that was the case until you wrote that in your reply. Thanks for that detail. The documentation could probably be improved to better explain how custom imagery sources can be added locally. (I still don't even know what format the file is meant to go in as -- a ​file:// URI or a plain path? -- but I'll try both.)

I also don't know what I did wrong here, nor what I did to warrant the condescension and hostility I've been provided. I pored over that entire page yesterday trying to work out how to make this work, and I don't think I'm an idiot for not having known a crucial detail that's completely undocumented. My goal with this ticket was to simply suggest a feature that would be nice for some use cases, and all of my communication here has been polite and in good faith. I don't think that warrants being told to "read the fucking manual" and "again: read before writing" as if I'm a willful idiot who's refusing to follow directions. I'm not sure what else I was supposed to do, besides learn how to read minds over the internet.