There is no defined generic semantic for the path and query parameters
in an URL. Semantic is only defined for the leading parts (protocol,
host, port etc.). How do you expect any mechanism to know that the
last part is a checksum (of what btw?)? I mean, completely
independent from technical questions of parsing: how would a piece of
software detect the checksum from looking at the URL?
For specific formatted URLs it’s a different story (see Sam’s
suggestion).
-----Messaggio originale-----
Da: Ryan D. [mailto:[email protected]]
Inviato: mercoled 23 novembre 2011 23:21
A: ruby-talk ML
Oggetto: Re: url normalization
On Nov 23, 2011, at 11:14 , rubix Rubix wrote:
automatically
I think if you pay close attention you’ll see that your browser goes to
the
first url and then gets redirected by the server to the second url. The
proper thing to do would be to actually do the redirection, not munge
the
url directly.
–
Caselle da 1GB, trasmetti allegati fino a 3GB e in piu’ IMAP, POP3 e
SMTP autenticato? GRATIS solo con Email.it http://www.email.it/f
I think if you pay close attention you’ll see that your browser goes to
the first url and then gets redirected by the server to the second url.
The proper thing to do would be to actually do the redirection, not
munge the url directly.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.