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

dev server proxy is not forwarding query params #598

Closed
1 of 5 tasks
thescientist13 opened this issue May 9, 2021 · 1 comment · Fixed by #599 or #608
Closed
1 of 5 tasks

dev server proxy is not forwarding query params #598

thescientist13 opened this issue May 9, 2021 · 1 comment · Fixed by #599 or #608
Assignees
Labels
bug Something isn't working CLI v0.12.1 v0.12.2
Milestone

Comments

@thescientist13
Copy link
Member

thescientist13 commented May 9, 2021

Type of Change

  • New Feature Request
  • Documentation / Website
  • Improvement / Suggestion
  • Bug
  • Other (please clarify below)

Summary

Noticed that in one of my projects, if I had a URL that had query parameters, they would not be included in the outbound URL.

Screen Shot 2021-05-08 at 5 51 38 PM

Details

For example, a URL like

/api/foo?query=xyz

When logged, would come out as

/api/foo

This might overlap with the solution for #578 so need to make sure both browser level URL query params and app request query params can all play nice.

@thescientist13
Copy link
Member Author

Still not fixed, looks like there is a major flaw in the current logic

return Promise.resolve(fs.existsSync(this.compilation.context.userWorkspace, bareUrl) || bareUrl === '/');

It should be using path.join before checking if the file fs.exists on disk, as right now it will always be true for userWorkspace 🤦

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment