also looking at this
fix(test): stop a leaked spawn mock hanging the gateway CLI tests (#2267), pin forwarded headers (#2265)
#2268
4 files
+57
-4
| @@ -183,6 +183,9 @@ describe('proxyViaPool', () => { | ||
| 183 | 183 | expect(got['x-forwarded-for']).toBe('203.0.113.7') |
| 184 | 184 | expect(got['x-real-ip']).toBe('203.0.113.7') |
| 185 | 185 | expect(got['x-forwarded-host']).toBe('site.test') |
| 186 | // rpx terminates TLS, so the upstream cannot otherwise tell the client arrived | |
| 187 | // over it — anything building absolute URLs or forcing HTTPS reads this. | |
| 188 | expect(got['x-forwarded-proto']).toBe('https') | |
| 186 | 189 | expect(got['x-custom']).toBe('keep-me') // unrelated client headers pass through |
| 187 | 190 | }) |
| 188 | 191 | |