We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
When using Ladle + vite-plugin-ssl with server.proxy, the following error appears on the server:
Internal server error: Header name must be a valid HTTP token [":path"]
I initially thought it's a regression of vitejs/vite#484, but turns out it's not: workaround for vitejs/vite#484 is still there. I dug down inside Ladle stuff and confirmed that the issue lies here:
ladle/packages/ladle/lib/cli/vite-dev.js
Lines 134 to 135 in ff434ef
This piece of code lacks the exact same workaround Vite lacked back in the days.
When I replaced these two lines of code with:
https .createServer(
Ladle + vite-plugin-ssl started working flawlessly with server.proxy.
Environment
System: OS: macOS 14.1.1 CPU: (8) arm64 Apple M2 Memory: 59.30 MB / 16.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 20.9.0 - /private/var/folders/3y/swkjq1x101b76mzjgt4pm2d80000gp/T/xfs-7e9663ff/node Yarn: 4.0.0 - /private/var/folders/3y/swkjq1x101b76mzjgt4pm2d80000gp/T/xfs-7e9663ff/yarn npm: 10.1.0 - /usr/local/bin/npm bun: 1.0.12 - ~/.bun/bin/bun Browsers: Chrome: 119.0.6045.159 Edge: 119.0.2151.72 Safari: 17.1
The text was updated successfully, but these errors were encountered:
I would like to work on this issue. Can you Please assign me this issue?
Sorry, something went wrong.
Sure, thanks!
Sanket-Arekar
Successfully merging a pull request may close this issue.
Describe the bug
When using Ladle + vite-plugin-ssl with server.proxy, the following error appears on the server:
I initially thought it's a regression of vitejs/vite#484, but turns out it's not: workaround for vitejs/vite#484 is still there. I dug down inside Ladle stuff and confirmed that the issue lies here:
ladle/packages/ladle/lib/cli/vite-dev.js
Lines 134 to 135 in ff434ef
This piece of code lacks the exact same workaround Vite lacked back in the days.
When I replaced these two lines of code with:
Ladle + vite-plugin-ssl started working flawlessly with server.proxy.
Environment
System: OS: macOS 14.1.1 CPU: (8) arm64 Apple M2 Memory: 59.30 MB / 16.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 20.9.0 - /private/var/folders/3y/swkjq1x101b76mzjgt4pm2d80000gp/T/xfs-7e9663ff/node Yarn: 4.0.0 - /private/var/folders/3y/swkjq1x101b76mzjgt4pm2d80000gp/T/xfs-7e9663ff/yarn npm: 10.1.0 - /usr/local/bin/npm bun: 1.0.12 - ~/.bun/bin/bun Browsers: Chrome: 119.0.6045.159 Edge: 119.0.2151.72 Safari: 17.1
The text was updated successfully, but these errors were encountered: