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
Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
Each OPTIONS request is automatically replaced with the 204 code type response, regardless the content and how the application intends to handle it.
OPTIONS type request is compliant with specification: https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
and should be handled respectively.
@angular-devkit/[email protected] uses [email protected] internally.
Commenting out or removing following code in (node_modules\webpack-dev-server\lib\Server.js) seems to fix this issue:
Command
serve
Is this a regression?
The previous version in which this bug was not present was
No response
Description
Each OPTIONS request is automatically replaced with the 204 code type response, regardless the content and how the application intends to handle it.
OPTIONS type request is compliant with specification:
https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
and should be handled respectively.
This refers to https://github.com/webpack/webpack-dev-server/issues/4551 and partially to #23857
Minimal Reproduction
Any application using proxy functionality and sending OPTIONS requests.
Please find a basic project to reproduce this issue here: https://github.com/sek1973/options-issue.
Exception or Error
Your Environment
Anything else relevant?
@angular-devkit/[email protected] uses [email protected] internally.
Commenting out or removing following code in (node_modules\webpack-dev-server\lib\Server.js) seems to fix this issue:
The text was updated successfully, but these errors were encountered: