It could be genuinely useful for testing HTTP clients if it had a wider array of... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		Retr0id 8 months ago \| parent \| context \| favorite \| on: No as a Service It could be genuinely useful for testing HTTP clients if it had a wider array of failure modes. Some ideas: - All the different HTTP status codes - expired/invalid TLS cert - no TLS cipher overlap - invalid syntax at the TLS and/or HTTP level - hang/timeout - endless slowloris-style response - compression-bomb - DNS failure (and/or round-robin DNS where some IPs are bad) - infinite redirect loop - ipv6-only - ipv4-only - Invalid JSON or XML syntax

zikani_03 8 months ago [–]

Not exactly what you are asking for, but reminded me that Toxiproxy[0] exists if you want to test your applications or even HTTP clients against various kinds of failures:

[0]: https://github.com/Shopify/toxiproxy

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact