Httpbin – HTTP Client Testing Service (opens in new tab)

IPv6 support would be great (take a look at what http://icanhazip.com does: http://ipv4.icanhazip.com and http://ipv6.icanhazip.com)

Anyway, sounds really cool :)

Endpoints to test various SSL/TLS/X.509 stuff would be super helpful. Call would returning a stock HTTP response body, but with different changes to the SSL/TLS handshake (you will have to use different host names to do this)

https://expired.x509.httpbin.org/ - returns an otherwise valid cert that has expired

https://wrongcn.x509.httpbin.org/ - returns an otherwise valid cert with a different CN name

https://sslv3.tls.httpbin.org/ - only negotiates an SSLv3 connection

https//3des.tls.httpbin.org/ - only negotiates to use 3DES as the cipher

I've wanted the ability to combine things – e.g. setting headers on a non-200 response. It'd be nice if there was a way to combine supported options into a single request or at least as many as will fit in to the querystring.

I'd like to see a method-neutral version of /get, /post, /patch et al - i.e. one that responds no matter what HTTP method is passed.

The response would then include "method": "BLAH" k/v indicating the method that was used.

http://ipinfo.io/ip (or http://ipinfo.io if you want geolocation info too).

You can also just Google it: https://www.google.com/#q=ip

http://checkip.amazonaws.com too

jsonip.org too :)

RequestBin isn't a substitute for HttpBin, they do 2 completely different things:

RequestBin = easily provision a url (useful for configuring a webhook) and inspect requests to that url.

HttpBin = pre-defined urls that return specific responses (headers & payloads). Good for testing http clients.

Fun fact: both tools are operated by the awesome people at http://Runscope.com.

This solves a problem that requestb.in does not. Namely, endpoints that predictably return various HTTP headers or HTTP content. This isn't about just testing to see what your app is sending. This is about testing how your application or HTTP client or whatever handles various weird HTTP responses and features.

If I need to test how my application responds to a relative URL in a Location header, I can hit the /relative-redirect/:n endpoint. Same for Absolute urls via /absolute-redirect/:n. The If-Not-Modified stuff is also helpful.

After seeing HTTP, then HTTPS, I was half-expecting the URL for that one to be eu://httpbin.org/

It was hosted in an EU-based datacenter on Heroku (to reduce latencies, not for any specific privacy reasons), but I need to check to see if we are still hosting it there.

With output in JSON/YAML/XML: http://mockbin.com/ip

I think it was something called 'ronn' https://github.com/Runscope/httpbin/issues/200