PUBLIC MARKS with tag http

how you can use Twisted Web's basic or digest HTTP authentication to control access to these resources.

SPDY veut notamment améliorer les délais de latence et diminuer le nombre de connexions nécessaires, avec un nombre «paquets» transmis plus faibles (mais plus denses en information). Les résultats, avec un prototype de serveur et un Chrome optimisé? Un chargement des pages 55% plus rapide.

Today we'd like to share with the web community information about SPDY, pronounced "SPeeDY", an early-stage research project that is part of our effort to make the web faster. SPDY is at its core an application-layer protocol for transporting content over the web. It is designed specifically for minimizing latency through features such as multiplexed streams, request prioritization and HTTP header compression.

GeoREST is a framework for accessing, distributing, and editing raw geospatial data over the web. Because it is based on REST, it supports searching using standard Web search engines such as Google and Bing.

a common format for archiving HTTP information that are captured by HTTP sniffers.

See HttpMethodsSupport for a review of toolkit support for HttpMethods. (OW)

J'étais en train de lire RESTful Email over HTTP et ça m'a rappelé un vieux vaporware, je me demande s'il ne serait pas intéressant de regrouper toutes les notifications en un unique endroit. Il suffirait pour cela d'accepter plusieurs choses en entrées :

* emails (pull/push)

* flux (pull)

* jabber (push)

* webhooks (push)

* irc (bonus !)

Django may be the Python web framework getting all the press recently, but web.py is definitely a nice, simple framework. One of the nice aspects of web.py is that it exposes methods for the basic HTTP methods (GET, POST, PUT, DELETE, etc.) and uses these methods to process each request from the client. This approach makes it amazingly easy to write a RESTful API.

Via Stefan, a proposal from the WSO2 gang for an approach to decentralizing media types and removing the requirement for the registration process.

In a plain HTTP interaction, the Content-type and Accept headers carry information about the type of the data being transmitted and accepted, respectively. You’ve seen these media types in numerous examples, e.g. a typical request or response might have a Content-type header with the value application/xml.

A significant weakness of HTTP in my view is its dependence on the MIME standard for media type identification and on the related iana registry. This registry is a limited bottleneck that does not have the capacity to deal with the media type definition requirements of individual enterprises or domains. Machine-centric environments rely in a higher level of semantics than the human-centric environment of the Web. In order for machines to effectively exploit information, every unique schema of information needs to be standardised in a media type and for those media types to be individually identified. The number of media types grows as machines become more dominant in a distributed computing environment and as the number of distinct environments increases.

remoteobjects are real subclassable Python objects on which you can build a rich API library. remoteobjects provides easy coding and transfer between Python objects and a JSON REST API. You can define the resources in a RESTful API as `RemoteObject` classes and their properties. These objects then support using the basic HTTP verbs to request and submit data to the API.

A RESTful, hypertext-driven system needs to enable clients to create a new resource that depends on three or more resources of different types. What's the best method to expose this capability?

When searching for something on the web we’ve all had the experience of clicking on a link in a search engine’s results page only to find that the page no longer exists. If there’s no information on that page other than a default error message, the most likely course of action on the user’s part is to press the back button and try the next search result.

As site authors we can make our error pages more meaningful to our users, so that an error becomes an opportunity to bring the user back into a site and show them content that’s relevant to what they’re looking for. In this article I’ll show you how to do just that.

API designers, please note the following rules before calling your creation a REST API:

Depending on the response's HTTP status the Location header has slightly different impact on the client's application state. The following table summarizes what I extracted from the HTTP spec.

ScriptServer is a minimalist application server, handling both GET and POST requests, including multipart/form-data for file uploads, HTTP redirections, and with an in-memory session management. It can run Python scripts and template files using the standard string substitution format

Most web pages include resources that change infrequently, such as CSS files, image files, JavaScript files, and so on. These resources take time to download over the network, which increases the time it takes to load a web page. HTTP caching allows these resources to be saved, or cached, by a browser or proxy. Once a resource is cached, a browser or proxy can refer to the locally cached copy instead of having to download it again on subsequent visits to the web page. Thus caching is a double win: you reduce round-trip time by eliminating numerous HTTP requests for the required resources, and you substantially reduce the total payload size of the responses. Besides leading to a dramatic reduction in page load time for subsequent user visits, enabling caching can also significantly reduce the bandwidth and hosting costs for your site.