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
..
admin	Updated tests eslint config to use eslint-plugin-ghost@0.5.0	2019-08-19 13:38:35 +01:00
api	💡Added v3 API endpoint (#11073)	2019-09-03 12:33:31 +05:30
middleware	🐛 Fixed 404s when using a proxy setup (#11269)	2019-10-28 11:22:05 +00:00
shared/middleware	Fixed spam prevention test being affected by order	2019-08-06 10:04:53 +01:00
parent-app_spec.js	🐛 Fixed 404s when using a proxy setup (#11269)	2019-10-28 11:22:05 +00:00
utils_spec.js	Refactored web/middleware and web/utils to web/shared (#9892)	2018-09-20 20:04:34 +02:00