0.3
This release contains some crucial bug-fixes that will allow config-gen
to work
with many more M2 setups - if you find an M2 installation where the proxy is not working,
please file an issue :)
fixes
-
forward redirects from proxy target (and upgrade them) 8a0a972
Some server configurations will redirect when a url is missing a trailing slash, which is now supported.
But we also noticed a case (when testing real-world server setups) where alocation
header contained
an insecure url, like accessinghttps://example.com
might redirect tohttp://example.com/uk
-
following that address would cause another redirect back to the secure versionhttps://example.com/uk
.The problem being that the
config-gen
proxy is only bound to a single port on the host machine, so
it cannot handle the 'middle' part of that chain (serving thehttp://example.com/uk
bit).The solution to this problem is to always upgrade the
scheme
in location headers to match the proxyscheme
.Problem solved, and it can now handle these weird server setups :)
-
should not enforce
yaml
for config files, should also allowjson
- fixes #25 a0f9289 -
should always bind to a random, available port unless overridden with
--port
- fixes #21 6c4879cWhen you run
config-gen
now, it will also run on a random port. To override this, provide--port
:# will bind to a random port config-gen https://example.com --config config.json # will try to bind to 9000, and will fail if it's unavailable config-gen https://example.com --config config.json --port 9000
-
should match (case-insensitive) on header values #27 57a94da
ci
- ensure
cargo fmt
was run on codebase e2d9a04 - add markdown badge d97858b
- remove experimental features to ensure builds on stable are ok 5a4d363
- fixed SSL support 55347de d70dabe
deps
- update to latest actix-web d8f42cd
tests