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

Internal server error: Header name must be a valid HTTP token [":path"] #536

Closed
wojtekmaj opened this issue Nov 24, 2023 · 2 comments · Fixed by #571
Closed

Internal server error: Header name must be a valid HTTP token [":path"] #536

wojtekmaj opened this issue Nov 24, 2023 · 2 comments · Fixed by #571
Assignees
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@wojtekmaj
Copy link
Contributor

wojtekmaj commented Nov 24, 2023

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:

http2
.createSecureServer(

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
@wojtekmaj wojtekmaj added the needs triage needs to be reviewed label Nov 24, 2023
@tajo tajo added bug Something isn't working good first issue Good for newcomers and removed needs triage needs to be reviewed labels Nov 24, 2023
@Sanket-Arekar
Copy link

I would like to work on this issue. Can you Please assign me this issue?

@tajo
Copy link
Owner

tajo commented Nov 28, 2023

I would like to work on this issue. Can you Please assign me this issue?

Sure, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants