-
Notifications
You must be signed in to change notification settings - Fork 218
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
Problems with POST-requests using routeRules in h3 > 1.7.1 #510
Comments
I am having same trouble. Upgrading from 1.7.1 to 1.8.0 breaks it even more.
|
same issue when upgrading from 1.7.1 to 1.8.0 |
Hi. Sorry for the inconvenience with upgrading. Since there is no minimal reproduction, I cannot confirm if unjs/ofetch#269 > unjs/ofetch#273 solved the same issue as you had but it seems was related (as you seem using proxy rules which was using ofetch as well) it would be nice if you could try to refresh your lockfile with latest dependencies to see if a problem exists. In case it still exists, and you can make a reproduction, please consider making a new issue in nuxt repository and ping me to investigate 🙏🏼 |
@ahoiroman I just updated to Nuxt 3.7.0 which uses [email protected] and my problem was solved, maybe you could give it a try, but my problem was only with files, other way it worked |
Yep, works with Nuxt ^3.7. Thanks :-) |
Please reopen, this does not work when it comes to DELETE requests. |
@pi0: As I found out, this happens, if the DELETE request, which is being made, does not have a body. If you add an empty body, it works as expected. |
Environment
Darwin
v20.5.0
3.6.5
-
[email protected]
vite
devtools
,modules
,routeRules
,colorMode
,runtimeConfig
,app
,imports
,i18n
,content
,image
,veeValidate
,ui
,googleFonts
@nuxt/[email protected]
,@nuxtjs/[email protected]
,@nuxthq/[email protected]
,@nuxt/[email protected]
,@vee-validate/[email protected]
,@nuxtjs/[email protected]
-
Reproduction
As stated at nuxt/nuxt#22645, I got an issue sending POST requests to proxied routes (routeRules with proxy).
The error only occurs, when these criteria are matched:
POST
body
- without body, the error does not occur (but - of course - the request is quite useless)Describe the bug
The following error is thrown:
Sending a CURL request gives the same result:
Additional context
Utility used to make requests to Laravel:
Logs
No response
The text was updated successfully, but these errors were encountered: