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

[BUG] Refit.ApiException: Response status code does not indicate success: 400 (Bad Request). #1388

Closed
wj8400684 opened this issue Jul 30, 2022 · 6 comments
Labels

Comments

@wj8400684
Copy link

wj8400684 commented Jul 30, 2022

The machine works normally, but an error is reported when it is placed on the server! Server version Windows Server 2022 datacenter 21h2!

@wj8400684 wj8400684 added the bug label Jul 30, 2022
@wj8400684
Copy link
Author

Reinstall solution!

@auvansangit
Copy link

auvansangit commented Oct 24, 2022

I have the same problem too, I can get response body, but after that poll retry the request due to status code 400
We use rancher k8s on centos

@noontz
Copy link

noontz commented Sep 9, 2023

Same exception thrown here when deployed to Azure Functions (in process) running on windows
(Refit 6.3.2, strict .NET6 LTS, POST method)
Works locally in simulated functions environment
Have tried [Body(buffered:true)] and custom implementation of IHttpContentSerializer as seen in #1122 (comment) with no luck
Even tried to pass in a string as [Body] replacing the sorcery in the serialization proces
It does not seem possible to create the request with Refit in this environment

Back to vanilla HttpClient 🥱

@anaisbetts
Copy link
Member

This doesn't seem related to Refit. If someone can provide more information that shows that it is related to Refit, please comment and we can reopen.

@noontz
Copy link

noontz commented Sep 11, 2023

@anaisbetts In my case you are absolutely correct, that this is not related to Refit. It was a configuration issue on Azure.

@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 26, 2023
@anaisbetts anaisbetts changed the title [BUG] Refit.ApiException: Response status code does not indicate success: 400 (Bad Request). at Refit.RequestBuilderImplementation.<>c__DisplayClass14_0`2.<<BuildCancellableTaskFuncForMethod>b__0>d.MoveNext() in /_/Refit/RequestBuilderImplementation.cs:line 288 --- End of stack trace from previous location --- [BUG] Refit.ApiException: Response status code does not indicate success: 400 (Bad Request). Sep 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants