wms_service_cache should use complete url - #3176
Open
JanEisermann wants to merge 15 commits into
Open
Conversation
Slugifying the normalized url collapses all url separators into "-", so distinct services map onto the same key, e.g. "http://a.com:1/wms" and "http://a.com/1/wms" both became "http-a-com-1-wms". The same happened for query parameters versus path elements. The normalized url is a fine dict key on its own, so keep it as is. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Cover the urls which collided when the key was slugified (port versus path element, host boundary, query parameters versus path) as well as the urls which have to share a key (GetCapabilities parameters, order of the remaining parameters, case of scheme and host) and the cache lookups of WMSServiceManager built on them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ReimarBauer
reviewed
Sep 3, 2026
ReimarBauer
reviewed
Sep 7, 2026
|
|
||
| :copyright: Copyright 2025 Reimar Bauer | ||
| :copyright: Copyright 2025-2026 by the MSS team, see AUTHORS. | ||
| :license: APACHE-2.0, see LICENSE for details. |
Member
There was a problem hiding this comment.
this looks like a new test module,
©️ Copyright 2026 Jan Eisermann
and there are currently no other contributions? by the team, or?
* added linux-aarch64 * missing platform added * readded 14
Added parameter and tests to _determinate_filename to fit its usage
* fix: serve chat attachments from a fixed URL namespace The relative path stored for a chat attachment was built from the *name* of the configured UPLOAD_FOLDER directory, while the chat blueprint serves attachments from the fixed route /uploads/<op_id>/<filename>. With a non-default UPLOAD_FOLDER (e.g. .../uploadshaha) the client therefore requested /uploadshaha/<op_id>/<filename>, got a 404 and an uploaded image was never shown, even though the file was stored correctly. Introduce ATTACHMENTS_URL_PREFIX and use it both for the route and for the path handed to the client, so the URL no longer depends on the directory name. The path is now also built with PurePosixPath, so it uses forward slashes on Windows as well.
Bumps [prefix-dev/setup-pixi](https://github.com/prefix-dev/setup-pixi) from 0.10.0 to 0.10.2. - [Release notes](https://github.com/prefix-dev/setup-pixi/releases) - [Commits](prefix-dev/setup-pixi@a09b624...d3f436a) --- updated-dependencies: - dependency-name: prefix-dev/setup-pixi dependency-version: 0.10.2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [zgosalvez/github-actions-ensure-sha-pinned-actions](https://github.com/zgosalvez/github-actions-ensure-sha-pinned-actions) from 5.0.5 to 5.0.7. - [Release notes](https://github.com/zgosalvez/github-actions-ensure-sha-pinned-actions/releases) - [Commits](zgosalvez/github-actions-ensure-sha-pinned-actions@3db98c0...c5fc58b) --- updated-dependencies: - dependency-name: zgosalvez/github-actions-ensure-sha-pinned-actions dependency-version: 5.0.7 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [coverallsapp/github-action](https://github.com/coverallsapp/github-action) from 2.3.7 to 2.3.8. - [Release notes](https://github.com/coverallsapp/github-action/releases) - [Commits](coverallsapp/github-action@5cbfd81...8d6379e) --- updated-dependencies: - dependency-name: coverallsapp/github-action dependency-version: 2.3.8 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [actions/checkout](https://github.com/actions/checkout) from 7.0.0 to 7.0.1. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@9c091bb...3d3c42e) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: 7.0.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose of PR?:
Fixes #2841
Does this PR introduce a breaking change?
use of a slugify version of the full url instead of the base_url in the wms_service_cache
If the changes in this PR are manually verified, list down the scenarios covered::
tests succeed, not manually verified
Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Does this PR results in some Documentation changes?
If yes, include the list of Documentation changes
Checklist:
<type>: <subject>