zenflow/composite-service-http-gateway

Configurable http gateway service for use with composite-service

composite-service-http-gateway's Issues

Stop accepting http requests when shutting down

When the http gateway receives a signal to shut down,
if should finish fulfilling any pending requests,
so that we aren't left with any incomplete "transactions",
but it should stop accepting any new requests,
so that it will actually be able to finish up and exit.

Is it possible to stop listening on the port without ending the active connections over that port?
If not, how should the gateway respond to new requests that are received after the shutdown signal? 500 status code?

HttpGatewayConfig validation

Currently the configuration passed to configureHttpGateway() is not validated in any way.

It should have some validation; it doesn't need to be as robust as the validation for CompositeServiceConfig.

Support Unix domain sockets as proxy targets

Instead of providing an TCP URL for a proxy target, you would be able to provide a Unix domain socket URL like unix:/path/to/socket.sock. This would come with performance benefits, but I'm not too familiar with how HTTP over Unix domain sockets works.

Support enforcing domain and or protocol using redirects

https://github.com/thenativeweb/forcedomain

Option to open the gateway URL in browser once gateway starts

Add HttpGatewayConfig.openBrowser: boolean defaulting to false. (Or see what other libraries call this option)

It might make sense to have the server listen on localhost instead of 0.0.0.0, since we can visit http://localhost:<port>/ in the browser (but not http://0.0.0.0:<port>/). edit: default host is now localhost