A Tale of 20 Cookies

As more applications move to leveraging the web, either through desktop-integration or complete migration to a web model, maintaining user state on the web becomes critical. For many web sites and applications this means the use of in-memory and persistent cookies. Netscape originally defined HTTP cookies in a preliminary document and later the IETF standardized…

5

Content-Encoding != Content-Type

RFC 2616 for HTTP 1.1 specifies how web servers must indicate encoding transformations using the Content-Encoding header. Although on the surface, Content-Encoding (e.g., gzip, deflate, compress) and Content-Type (e.g., x-application/x-gzip) sound similar, they are, in fact, two distinct pieces of information. Whereas servers use Content-Type to specify the data type of the entity body, which…

6

Wanted: Developer feedback for our "Next Generation" client HTTP stack

As we begin the planning phase for our “Next Generation” client HTTP stack, we would love to hear from developers using our existing APIs (WinINet and WinHTTP). Please help us understand what your experience has been so far and what you would like to see in any future releases by filling out this survey. Thanks  -Jonathan Silvera

5

What’s next on the client HTTP stack front

http://www.microsoft-watch.com/article2/0,2180,1940567,00.aspHachamovitch acknowledged Microsoft already is building the next two versions of IE. He declined to offer guidelines on delivery schedules or feature sets, other than to say one of the two versions will include “a complete reworking of the networking stack.” That would be us. We are going to be busy for awhile 🙂 –…

6