Skip to content

fix for #612 #613

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

Merged
merged 1 commit into from
Sep 21, 2016
Merged

fix for #612 #613

merged 1 commit into from
Sep 21, 2016

Conversation

skwakman
Copy link
Contributor

Please check if the PR fulfills these requirements

  • An example has been added or updated in examples/ (for features)
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Other... Please describe:

What is the current behavior? (You can also link to an open issue here)
See #612

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No (as far as I know)

If this PR contains a breaking change, please describe the following...

Other information:

added additional middleware feature to express' use-chain after proxy to enable proxy-bypass retrievals to in-memory resources. Fixes #612.

added additional `middleware` feature to express' use-chain after proxy to enable proxy-bypass retrievals to in-memory resources. Fixes webpack#612.
@SpaceK33z
Copy link
Member

Thanks.

@SpaceK33z SpaceK33z closed this Sep 21, 2016
@SpaceK33z SpaceK33z reopened this Sep 21, 2016
@SpaceK33z
Copy link
Member

Whoops, accidentally closed.

@SpaceK33z SpaceK33z merged commit 5cc0126 into webpack:master Sep 21, 2016
@skwakman skwakman deleted the patch-1 branch October 4, 2016 10:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

in-memory resources are not loaded after proxy bypass
2 participants