Ghost/core/test/unit
Kevin Ansfield 7284227f1e
🐛 Fixed 404s when using a proxy setup (#11269)
no issue

When using certain proxy setups that result in `host` and `x-forwarded-host` being different, it became impossible to access Ghost because all routes showed generic 404 pages.

- `vhost` module that we are using to separate front-end and admin urls does not use express' `req.hostname` so it does not pick up the `x-forwarded-host` url that express' `'trust proxy'` config gives us
- switched to the forked `@tryghost/vhost-middleware` package which has a one-line change to use `req.hostname || req.host`
- added `'trust proxy'` config to the admin express app and switched to using `req.hostname` in our redirect code to avoid infinite redirect loops
2019-10-28 11:22:05 +00:00
..
adapters ⚠️ Skiped Scheduler initialization logic and it's tests 2019-09-11 18:27:57 +02:00
api Merge branch 'master' into v3 2019-10-08 13:58:08 +01:00
apps Removed subscribers from the codebase (#11153) 2019-10-09 11:47:04 +02:00
config Updated tests eslint config to use eslint-plugin-ghost@0.5.0 2019-08-19 13:38:35 +01:00
data 💄Updated fixtures for Ghost v3 content + assets (#11247) 2019-10-17 10:49:30 +02:00
helpers Removed begin/end html comments from output of most cards 2019-09-20 14:31:42 +01:00
lib Merge branch 'master' into v3 2019-10-11 11:31:31 +01:00
models Merge branch 'master' into v3 2019-10-11 11:31:31 +01:00
services Correct Twitter username 2019-10-16 14:22:42 +07:00
web 🐛 Fixed 404s when using a proxy setup (#11269) 2019-10-28 11:22:05 +00:00