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

WebClient - ClientResponse does not expose any information about the originating request #30547

Closed
nlescure-pictet opened this issue May 25, 2023 · 1 comment
Labels
status: duplicate A duplicate of another issue

Comments

@nlescure-pictet
Copy link

Hi,

In order to improve error processing (or else) it would be nice to be able to get access to some request attributes (like url, headers, ...) AFTER the retrieve / exchangeToXXX operators. I was thinking about a getRequest() method in the ClientResponse (as it is actually the case in the DefaultClientResponse) so that on(Raw)Status or exchangeToXXX operators could have access to some of the request attributes.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label May 25, 2023
@snicoll
Copy link
Member

snicoll commented Nov 29, 2023

Thanks for the suggestion. This has been added in 6.1, see #28397

@snicoll snicoll closed this as not planned Won't fix, can't repro, duplicate, stale Nov 29, 2023
@snicoll snicoll added status: duplicate A duplicate of another issue and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: duplicate A duplicate of another issue
Projects
None yet
Development

No branches or pull requests

3 participants