James Bain comments

Repositories
Issues
Comments

Results 3 comments of


                                            James Bain

Header encoding error for custom response headers: Invalid character in header content ["custom-response-header"]

Good catch. So I think then the relevant section is 3.2.4 of RFC 7230 https://www.rfc-editor.org/rfc/rfc7230#section-3.2.4. > Historically, HTTP has allowed field content with text in the [ISO-8859-1](https://www.rfc-editor.org/rfc/rfc7230#ref-ISO-8859-1) charset [ISO-8859-1], supporting...

Allow for dynamic websocket upstreams with `replyOptions.getUpstream`

> Thanks for reporting! Would you like to send a Pull Request to address this issue? Remember to add unit tests. Yeah, I can do that!

Allow for dynamic websocket upstreams with `replyOptions.getUpstream`

Sorry for the silence. After further review, it appears that this functionality does work with dynamic websocket proxying endpoints but only for the `upstream` option and not the `wsUpstream`. I'm...