"The most impressive request thoroughly embraced the nature of TCP/IP, and arrived in a number of packets, out of order and with some data corruption (see the missing data on the envelopes), which we had to reconstitute into the actual request within our ‘server’." Everyone involved in this post is brilliant.

This is remarkably detailed.

If you have MacPorts installed, OpenSSL runs into issues when you install rubies through RVM. This helps.

"I've been working on a sketch wherein some data is downloaded from an HTTP server and is then processed on the Arduino (printed, as it happens, but I don't think that's important). In my original sketches, I was occasionally seeing transfers fail midway through." James is running into issues that might be relevant to me.

"RequestBin lets you create a URL that will collect requests made to it, then let you inspect them in a human-friendly way. Use RequestBin to see what your HTTP client is sending or to look at webhook requests." Which is very useful.

"A Mac OS X Leopard developer tool for debugging HTTP services by graphically creating & inspecting complex HTTP messages." Oh, that could come in handy.

"Recently I had been wondering what the complete list of HTTP status code symbols was in Rails. Searching through Rails didn't yield any results for a symbol like :unprocessable_entity... Rails defines the symbol to status code mapping dynamically from the status message. The symbol used is an underscored version of the status message with no spaces." Quick list of clear textual shorthand for returning HTTP status.

"Fiddler is a HTTP Debugging Proxy which logs all HTTP traffic between your computer and the Internet. Fiddler allows you to inspect all HTTP Traffic, set breakpoints, and "fiddle" with incoming or outgoing data."

There is a place for browser drivers (like Selenium or Sahi) and for suites based on browser emulation techniques (such as HTTPUnit or Twill). Knowing which to use and when can result in significant time savings when running your test suites.

Lots of useful information in here - but implementing it is more problematic, depending on your setup.

Don’t let tools tell you how to form your URIs, and certainly don’t let them force you to serve your content in a particular way.

Interesting, simple explanation of TCP/IP and API design in Ruby

Really good, simply explanation, of how to write REST protocols

Might be interesting.