4 ms·
We did require some of them[1]. Esp. painful were Transfer-Encoding quirks, and some dances around old HTTP/1.0 backends and request buffering. Compared to NG
by SaveTheRbtz 6y ago
We did require some of them[1]. Esp. painful were Transfer-Encoding quirks, and some dances around old HTTP/1.0 backends and request buffering.
Compared to NGINX though, it was relatively easy to push these fixes upstream. Community is very welcoming to outside contributions.
[1] https://dropbox.tech/infrastructure/how-we-migrated-dropbox-from-nginx-to-envoy#-issues-we-encountered- https://dropbox.tech/infrastructure/how-we-migrated-dropbox-...
- veshij 6y agoWe do have some local patches as well (mostly for integration with out own infrastructure - stats collection, some RPC specific stuff). As SaveTheRbtz mentioned we encountered some issues with non-RFC clients, corner cases which were not exposed when envoy is used in "trusted" environment, etc., but all our fixes are now in upstream, so next migrations will be way easier both for us and for other envoy users.