You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
How to clear fragment of RequestTemplate (Feign client 11.10)? #3095
When I do template.target(newTarget); template.uri(newUri ); in my custom RequestInterceptor ,
I noticed that the origin fragment was kept in final URL (something like https://newTarget/newPath?newQuery=newVal#oldFragment , the oldFragment is not part of newUri).
The best thing I can do is template.uri(newUri +"#"); and I will get https://newTarget/newPath?newQuery=newVal# .
How to fully clear fragment, so I can get https://newTarget/newPath?newQuery=newVal ?
changed the title [-]How to clear fragment of RequestTemplate (Feign client)?[/-][+]How to clear fragment of RequestTemplate (Feign client 11.10)?[/+]on Oct 24, 2025
Thanks for the report. This project is community-maintained, and the maintainer won't implement fixes/features directly. If you want this to move forward, please open a pull request with automated tests that cover the change.
I can take this. I’ll cover replacing a URI that previously had a fragment, while keeping the append behavior explicit. I also found that target() decodes an escaped fragment before appending it to the URL; I’ll check that in the same fragment-handling tests.
I’ll keep the change inside RequestTemplate, with no new public setter.
AI-assisted investigation and implementation for @hutiefang76.
Activity
[-]How to clear fragment of RequestTemplate (Feign client)?[/-][+]How to clear fragment of RequestTemplate (Feign client 11.10)?[/+]velo commentedon May 27, 2026
Thanks for the report. This project is community-maintained, and the maintainer won't implement fixes/features directly. If you want this to move forward, please open a pull request with automated tests that cover the change.
hutiefang76 commentedon Oct 19, 2026
I can take this. I’ll cover replacing a URI that previously had a fragment, while keeping the append behavior explicit. I also found that
target()decodes an escaped fragment before appending it to the URL; I’ll check that in the same fragment-handling tests.I’ll keep the change inside RequestTemplate, with no new public setter.
AI-assisted investigation and implementation for @hutiefang76.
Fix URI fragment replacement and preserve target escapes (#3633)