>>>>> On Wed, 16 Mar 2011, Jeroen Roovers wrote: > "An HTTP URL takes the form:
> http://<host>:<port>/<path>?<searchpart> > "where <host> and <port> are as described in Section 3.1. If :<port> > is omitted, the port defaults to 80. No user name or password is > allowed. <path> is an HTTP selector, and <searchpart> is a query > string. The <path> is optional, as is the <searchpart> and its > preceding "?". If neither <path> nor <searchpart> is present, the "/" > may also be omitted." [1] Right, so <http://emboss.sourceforge.net> or even <http://emboss.sourceforge.net:80> are legal and equivalent to <http://emboss.sourceforge.net/>. However, there is also a "normalized form" of URIs, which does include the trailing slash: "In general, a URI that uses the generic syntax for authority with an empty path should be normalized to a path of "/"." [2] Ulrich > [1] <http://www.ietf.org/rfc/rfc1738.txt>, p.8, section 3.3 [2] <http://tools.ietf.org/html/rfc3986#section-6.2.3>
