-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
in-memory resources are not loaded after proxy bypass #612
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
Comments
skwakman
added a commit
to skwakman/webpack-dev-server
that referenced
this issue
Sep 21, 2016
added additional `middleware` feature to express' use-chain after proxy to enable proxy-bypass retrievals to in-memory resources. Fixes webpack#612.
PR welcome. |
Can this fix also be merged for the 1.x branch? |
skwakman
added a commit
to skwakman/webpack-dev-server
that referenced
this issue
Sep 21, 2016
SpaceK33z
pushed a commit
that referenced
this issue
Sep 21, 2016
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
When using
proxy
'sbypass
function, resources that are bypassed and are part of the in-memory webpack bundle are not retrieved. Instead, only files from the filesystem are retrieved.Example:
Running the server using
--inline
I've fixed this locally by manually editing
webpack-dev-server
'sServer.js
file:webpack: tested with 1.13.2, although bug is in server, not in webpack itself
webpack-dev-server: confirmed on 1.16.1 but might also be present in 2.x
OS: OSX 10.11.6, local installation
The text was updated successfully, but these errors were encountered: