Paul Colomiets
Paul Colomiets
There are some servers that don't obey non-body receiving responses, including: 1. Sending 0-length chunk on 304 Not Modified 2. Sending full response body in HEAD requests 3. Sometimes nginx...
Currently, swindon doesn't expect (and doesn't send) *any* response even if `Transfer-Encoding` and `Content-Length` are specified on such codes. For server part it's easy: just don't send `Transfer-Encoding`, but client...
I.e. I get this error even if I don't remove/add session pools: ``` 2017-07-29T22:18:19Z [swindon::chat::listener::pools] ERROR: Error listening 127.0.0.1:2007: Address already in use (os error 98). Will retry on next...
`btree_range` feature is stable since rust 1.17.0, so we can fix the respective [todo lines](https://github.com/swindon-rs/swindon/blob/94e0bede88dc9b6b88122e9e31ee1c91be1e5801/src/routing.rs#L124-L125)
`tangle/` name is historical accident. The migration strategy is basically following: 1. Reserve `swindon.*` prefix in some swindon version 2. Put `swindon.*` into config into `dest/tangle/*` (add a requirement? warning?)...
Currently, we return 404, which is kinda okay, but not always clear at the development stage. Maybe just log the error.
I.e. it should work for any domain except those specified in routing specifically. We can try to make it more clear or warn or hint users for doing this. I'm...
If backend publishes message by multiple requests to swindon it's both: 1. Inefficient (two HTTP requests) 2. Some clients (subscribed to both topics) receive message twice
As the step one we just fetch addresses from external source: ``` http-destinations: my-application: addresses: !JsonRequest verwalter/v1/schedule?key=data.roles.my-application.all_backends verwalter: addresses: - localhost:8379 ``` More comprehensive settings might look like: ``` htttp-destinations:...