Skip to content
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

Fix request request path to always include leading slash / #2452

Merged
merged 2 commits into from
Dec 16, 2024

Conversation

schlosna
Copy link
Contributor

Before this PR

#2437 introduced an issue where requests with an empty path were no longer rendered with a leading slash.

prior to 4.6.0 render URLs like:
https://localhost:59845/?REQUEST=GetCapabilities&SERVICE=WMS

4.6.0 renders them like:
https://localhost:59845?REQUEST=GetCapabilities&SERVICE=WMS

Specifically see org.apache.hc.core5.http.support.AbstractRequestBuilder#setUri(java.net.URI)

After this PR

==COMMIT_MSG==
Fix request request path to always include leading slash /
==COMMIT_MSG==

Possible downsides?

@changelog-app
Copy link

changelog-app bot commented Dec 15, 2024

Generate changelog in changelog/@unreleased

What do the change types mean?
  • feature: A new feature of the service.
  • improvement: An incremental improvement in the functionality or operation of the service.
  • fix: Remedies the incorrect behaviour of a component of the service in a backwards-compatible way.
  • break: Has the potential to break consumers of this service's API, inclusive of both Palantir services
    and external consumers of the service's API (e.g. customer-written software or integrations).
  • deprecation: Advertises the intention to remove service functionality without any change to the
    operation of the service itself.
  • manualTask: Requires the possibility of manual intervention (running a script, eyeballing configuration,
    performing database surgery, ...) at the time of upgrade for it to succeed.
  • migration: A fully automatic upgrade migration task with no engineer input required.

Note: only one type should be chosen.

How are new versions calculated?
  • ❗The break and manual task changelog types will result in a major release!
  • 🐛 The fix changelog type will result in a minor release in most cases, and a patch release version for patch branches. This behaviour is configurable in autorelease.
  • ✨ All others will result in a minor version release.

Type

  • Feature
  • Improvement
  • Fix
  • Break
  • Deprecation
  • Manual task
  • Migration

Description

Fix request request path to always include leading slash /

Check the box to generate changelog(s)

  • Generate changelog entry

@schlosna schlosna requested a review from bjlaub December 15, 2024 23:22
@bulldozer-bot bulldozer-bot bot merged commit 965f9a1 into develop Dec 16, 2024
6 checks passed
@bulldozer-bot bulldozer-bot bot deleted the davids/apache-client-url branch December 16, 2024 02:45
@autorelease3
Copy link

autorelease3 bot commented Dec 16, 2024

Released 4.7.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants