Re: IE vs Firefox -- http:// matters?

Just guessing, but # in this case probably stands for number, i.e. my
port
number, not a literal pound/hash/whatever sign.

[email protected]
wrote:

The app is at http://www.mydomain.com:myport#/app/list

That’s not a valid URL.

Just to clarify, while that’s probably
not something you want to be
confusing webservers with, it -is- a valid
URI according to RFC 3986.
(FYI, Rob, http://www.ietf.org/rfc/rfc3986.txt
obsoletes RFC 2396.)

Parsed out, it works out to:

scheme: “http”

authority: “www.mydomain.com:myport”
path: “”
query: nil
fragment:
“/app/list”

If you apply the simple scheme-based normalization algorithm
(in this
case, http-based) described in RFC 3986, you end up with the following

URI, and I believe that’s what Firefox does:

http://www.mydomain.com:myport/#/app/list

Cheers,
Bob A.

AIM: sporkmonger
Jabber: [email protected]


Rails mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs