PUBLIC MARKS with tag http

Generally speaking, web pages on high latency connections with high numbers of embedded objects will see the biggest benefit from SPDY.

spire.io provides, as its foundation, a simple REST API. As such, the first thing you do is some discovery to get all the URLs you need to get started.

There has been a lot of frustration lately about layered systems in computer science and especially the Web.

There seems to be broad agreement that the time is ripe to start work on a new version of HTTP in the IETF, and that it should happen in this Working Group.

The growing interest in both the SPDY protocol and Node.js created the need for a stable Node.js SPDY module when the first version was released last year.

With this module you can create SPDY servers in node.js with natural http module interface and fallback to regular https (for browsers that doesn't support SPDY yet).

As with anything, there are downsides to using this technique. The main one being no more interactivity. If your website had a commenting feature built in, it won’t work anymore. If it ran off a CMS like WordPress, you won’t be able to log in and make edits to your content. Everything is now static HTML, forever.

There are some broken HTTP clients out there. I've run into one: Flash (circa 2009). Flash gets upset if it doesn't receive a 200 response from the server. In particular, if your server returns a 4xx HTTP code in an API response, Flash will not even pass the response to the Flash application.

An interactive shell for issuing HTTP commands to a web server or REST API.

HTTP Status Cats

POST only becomes an issue when it is used in a situation for which some other method is ideally suited: e.g., retrieval of information that should be a representation of some resource (GET), complete replacement of a representation (PUT), or any of the other standardized methods that tell intermediaries something more valuable than “this may change something.”

The goal is simple : check that a set of web services are HTTP compliant.

Your APIs should do this. There should be a single endpoint for the resource, and all of the other actions you’d need to undertake should be able to be discovered by inspecting that resource.

One final approach that I find very interesting was mentioned by Jan Algermissen a while ago: If your format is based on an existing one, e.g. HTML or XML, your server can actually send the same content with different MIME types, depending on the client’s capabilities. A client that only included application/json in its Accept header would then get the content labeled application/json, while one that includes the specific MIME type application/vnd.whatever would get the same content with this label applied.

A user’s cache can only hold less than a day’s worth of browsing data: An average user browses 88 pages/day, an average page weighs 930KB, and most desktop browsers cache no more than 75MB of data. For mobile, the ratio is even worse.

ql.io – a declarative, evented, data-retrieval and aggregation gateway for HTTP APIs. Through ql.io, we want to help application developers increase engineering clock speed and improve end user experience. ql.io can reduce the number of lines of code required to call multiple HTTP APIs while simultaneously bringing down network latency and bandwidth usage in certain use cases.

karl says: Your comment is awaiting moderation. December 2, 2011 at 2:51 pm There is a missing opportunity from both monolingual search engines and content providers. It’s kind of sad. The fact to have one unique URI that a French user can just paste to his Japanese friend is one wonderful thing of content negotiation. How do we leverage this, so search engines are able to understand it? Enter the never used 1998 RFC: “Transparent Content Negotiation in HTTP” (RFC 2295). http://tools.ietf.org/html/rfc2295 I wonder what it would take for Google to negotiate with content providers and offering this feature. The solution is super simple. We were living in a world where sites were quite monolingual but this has changed since.

Gestion des URL SPIP3 permet la gestion des URL. Une fois modifiées, les anciennes URL redirigent les utilisateurs vers les nouvelles.

For my money any tool or Web framework worth writing your code inside out for should fire up a dentist's drill, slap you around the face and repeatedly ask IS IT SAFE? until it GET's a straight answer.

The Content-Length is nearly 2GB. Which is obviously not conforming to the HTTP standard.

here is the proposed sequence of steps in this scenario: clients GET the template and a token from the factory resource. since this operation does not change server state, it is safe and idempotent and it is possible to use GET. clients PUT to the token URI, at which point the server creates and populates the resource at the repository level, and keeps track of the token from which the resource has been created. the server responds with a 303 (See Other) response, indicating the persistent URI of the resource. subsequent requests to the token URIs are handled with a 301 (Moved Permanently) response, telling clients that the token URI should no longer be used, and that a persistent URI is now available.

We present results of a 45-participant laboratory study investigating the usability of tools to limit online behavioral advertising (OBA).We tested nine tools, including tools that block access to advertising websites, tools that set cookies indicating a user’s preference to opt out of OBA, and privacy tools that are built directly into web browsers. We interviewed participants about OBA, observed their behavior as they installed and used a privacy tool, and recorded their perceptions and attitudes about that tool. We found serious usability flaws in all nine tools we examined. The online opt-out tools were challenging for users to understand and configure. Users tend to be unfamiliar with most advertising companies, and therefore are unable to make meaningful choices. Users liked the fact that the browsers we tested had built-in Do Not Track features, but were wary of whether advertising companies would respect this preference. Users struggled to install and configure blocking lists to make effective use of blocking tools. They often erroneously concluded the tool they were using was blocking OBA when they had not properly configured it to do so.