https://addons.mozilla.org/en-US/firefox/addon/2691/
This link is now broken.
about:
A developer tool for interacting with web services and other web resources that lets you make HTTP requests, set the entity body, and content type. This allows you to interact with web services and inspect the results...
very neat and useful indeed!
Bouncer is a real time statistics and security engine written in PHP5. It analyses the browser or bot version, and detects eventual bad behaviors in order to prevent spam.
Charles is an HTTP proxy / HTTP monitor / Reverse Proxy that enables a developer to view all of the HTTP and SSL / HTTPS traffic between their machine and the Internet. This includes requests, responses and the HTTP headers (which contain the cookies and caching information).
Seems to be little more usable than wireshark!
Birdfeeder is the prototype implementation of a RESTful, interoperable, Internet-scale microblogging protocol, tentatively called Fethr (Featherweight Entangled Timelines over HTTP Requests). It proposes all the traditionnal features of the microblogging. Can be tested at http://river.cs.rice.edu/bird/
Sure the most funny IETF RFC that I have been given to read. This document specifies a Hyper Text Coffee Pot Control Protocol (HTCPCP), based on HTTP, which permits the full request and responses necessary to control all devices capable of making the popular caffeinated hot beverages.
http://www.recessframework.com/
This link is now broken.
about:
The Recess! Framework is built from the ground up to conform to the HTTP protocol. This makes REST a natural fit. From 100s to 505s, from GETs to PUTs, Recess! makes it straightforward for your web apps to play nice
Given the current projects I am working on, I daily see misuse of content-negotiation methodology, particularly the misuse of the Accept and Content-type HTTP header parameters.
http://blog.phpdeveloper.co.nz/2006/10/25/ssl-redirect-filter-for-symfony/
This link is now broken.
about:
Serving secure pages on a website is made a lot easier by having both your secure and insecure pages served by the same files - all you need to do is change the scheme from http:// to https:// and you're done. But how do you manage which pages should redirect to the secure server? And how do you make sure you redirect users back when they're finished submitting sensitive information?
