New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: Use CPLSetConfigOption/CPLGetConfigOption for some CGI/FastCGI-related env vars. #6304
Conversation
… instead of the env (mostly for IIS/FastCGI).
This will be a great help Steve, as MS4W has had to do workarounds for this issue for several years, so that users never had to deal with this problem (also affects MapCache at /mapcache/lib/http.c ...will file that ticket now for MapCache). PS> this issue is not just for IIS. |
Will wait on merging until folks actually confirm it helps in various environments - mostly Windows CGI and FastCGI. |
@sdlime - many thanks for this! I've built and tested on a fresh Windows 10/ IIS 10 install. All environ variables are now read correctly, with cascading WMS over HTTP now possible thanks to being able to use the I've updated the IIS docs in preparation for this being merged: MapServer/MapServer-documentation#517 |
Should I redo this against main? Seems like it and then we'd backport to wherever. I've not done a rebase before though... |
Potential solution for IIS/FastCGI where we push some high-value environment variables into the CPL environment (using CPLSetConfigOption) and then reference them there (CPLGetConfigOption). This is against branch-7-6 rather than main since the config file work would replace this.
Should be ok for non-IIS/FastCGI as well.
--Steve