InfoQ Homepage HTTP Content on InfoQ
-
SPDY versus WebSockets?
Lori MacVittie has recently posted an article describing why she believes SPDY will gain much wider acceptance in the Web than WebSockets. For her and several others, the differentiating aspect between these protocols is the way in which they use HTTP and SPDY wins because of this.
-
Home Document Format for Non-Browser HTTP Clients
On behalf of the IETF, Mark Nottingham has recently published a draft of the Home Documents for HTTP APIs specification. Intended for non-browser clients, it provides a way to describe resources available from a particular site as well as possible hints on how to interact with those services.
-
Google and Microsoft Want to Improve HTTP
Google and Microsoft want to improve HTTP with SPDY and Speed+Mobility. This article reviews both proposals outlining what benefits they bring to the much used Internet protocol.
-
HTTPbis Working Group Start To Consider HTTP/2.0
Rackspace's Mark Nottingham, discusses the recent HTTPbis Working Group meeting, clarifications to the HTTP/1.1 specification, and the influence of SPDY on the group that have resulted in a change to its charter enabling them to begin considering HTTP/2.0.
-
Security vulnerabilities with HTML5 (WebSockets)?
Lori Macvittie recently raised concerns about WebSockets vulnerabilities to viruses and malware due to the removal of HTTP headers and MIME types. Given other reported security issues with the protocol and implementations, is it time to step back and consider what a world based on WebSockets should look like?
-
Apache Celebrates 17th Anniversary with HTTP Server 2.4
Apache has released the HTTP Server version 2.4 with performance improvements, enhanced concurrency, asynchronous I/O support, lower resource footprint and others.
-
Netty 3.3.1 Release Supports SPDY Protocol
The Netty 3.3.1 release adds support for SPDY protocol, which has been proposed for inclusion in http/2.0, fixes regression of Android support and reduces memory consumption of ZLib compression.
-
Best Practices For HTTP API Evolvability
As the title suggests, in Best Practices For HTTP API Evolvability, Benjamin Carlyle, set out to define priciples and practices for designing systems, that are built around HTTP API’s. Systems, that are extensible and can evolve over time.
-
Restfuse 1.0.0 - A Library For Easy REST/HTTP Integration Tests
EclipseSource has released the first stable version for an open source JUnit extension that automates testing of REST/HTTP services supporting both synchronous and asynchronous calls.
-
"Apache Killer" a DDoS using the Range HTTP Header
The "Apache Killer" lets an attacker use a single PC to wage a denial of service attack against an Apache server. So far, the Apache development team has issued an alert and workarounds in advance of rolling out a patch for the flaw in Apache HTTPD Web Server 1.3 and 2.X, but no patches.
-
Is it Difficult to Write REST Clients?
Adam DuVander, from the Programmable Web, reported last week on a survey of API experiences which raised some of the largest problems developers encounter in consuming Web APIs, including the most popular APIs.
-
Twentieth Anniversary of the World Wide Web
This weekend represented the 20th anniversary of the announcement of the World Wide Web. The length of a patent is twenty years; had the first server been patented then we would only now be able to innovate on top of one of the cornerstones of today's global economy.
-
Should the Web be Encrypted?
Last week, the Electronic Frontier Foundation (EFF), in collaboration with the Tor Project, has launched an official 1.0 version of HTTPS Everywhere, a tool for the Firefox web browser that helps secure web browsing by encrypting connections to more than 1,000 websites.
-
On Building Evolvable Systems
In a recent post Mike Amundsen writes about building evolvable systems where he expands on his presentation "Beyond REST : An approach for crafting stable, evolve-able Web applications". The question he hopes to answer in the presentation is "How can we design and implement distributed network solutions that remain stable and flexible over time?"
-
Opinion: Tim Bray on the Web vs Native Debate
Tim Bray who spoke recently in Seattle about this topic published today a long post on the Web vs Native Mobile Application Debate. If the game seems open today, can the Web applications remain competitive and eventually win the mobile game? Can HTTP itself remain the protocol of choice in a power and bandwidth constrained environment where bi-directional telephony protocols play equally well?