This section contains articles about new standards or improvements to existing ones. At some point I’ll try to submit these formally to the IETF or the JCP, but for now, they’re here for general dissemination and discussion.

Any inventions described in these articles are hereby licensed to the Internet community at no chage, provided that attribution is made to me in any descriptions of the use of these inventions. In addition, it is strongly recommended that use of these inventions be made in strict adherence to these descriptions, so as to enhance their suitability as Internet Standards. If you find that you cannot use these methods strictly as described, you are encourage to about improving these descriptions to accommodate your needs.

SSL HTTP Proxies

When URIs are rendered in the responses of secure dynamic web resources (servlets, JSPs, etc), certain consideration must be taken regarding the use of http and https schemes. Specifically, the response markup of a secure resource containing hyperlinks to non-secure resources need to be rendered as absolute URIs with http (non-secure) scheme. Similarly, although less important, URIs to secure resources rendered into unsecure responses need https schemes. This article discusses a method for SSL HTTP Proxies to provide information to the origin server about the original request, so that it may act accordingly.

Enhancements to the Java Servlet Specification

The need to render HTTP URIs that use non-standard port numbers is common in development and production environments alike. This article discusses a standard method by which web application code can determine which ports are currently configured for http and https requests.

Enhancements to RFC 1808, “Relative URLs”

It would be helpful in some instances be able to change the scheme used by a relative URL without specifying a complete, absolute URI. This article discusses some of issues surrounding this ability.