Yes upper and lower case are both allowed, but (to quote your second
reference) "the other generic syntax components are assumed to be case-
sensitive unless specifically defined otherwise by the scheme".  Seems
the specs aren't any more specific than that, leading to
implementation-specific behaviour.

So it's not impossible but it has its downsides.  Just how badly to
you want to do it?

Mike

On Jul 13, 6:13 pm, Graham Higgins <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 13 Jul 2010, at 14:36, mohammed.ali.eng wrote:
>
> > it's depends on server,
>
> It may seem that way but that's just the implementation. The  
> appropriate standards-setting docs would seem to be RDF1738 [1] and  
> later, for URIs, RFC3986 [2]. Both are clear about the character  
> content of http-urls / uris. Both provide descriptions in BNF, e.g.  
> this BNF fragment from RFC 1738 (where "urlpath" is the focus of our  
> interest) ...
> urlpath = *xchar ; depends on protocol see section 3.1
> [...]
> lowalpha       = "a" | "b" | "c" | "d" | "e" | "f" | "g" | "h" |
>                   "i" | "j" | "k" | "l" | "m" | "n" | "o" | "p" |
>                   "q" | "r" | "s" | "t" | "u" | "v" | "w" | "x" |
>                   "y" | "z"
> hialpha        = "A" | "B" | "C" | "D" | "E" | "F" | "G" | "H" | "I" |
>                   "J" | "K" | "L" | "M" | "N" | "O" | "P" | "Q" | "R" |
>                   "S" | "T" | "U" | "V" | "W" | "X" | "Y" | "Z"
> alpha          = lowalpha | hialpha
> digit          = "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" |
>                   "8" | "9"
> safe           = "$" | "-" | "_" | "." | "+"
> extra          = "!" | "*" | "'" | "(" | ")" | ","
> reserved       = ";" | "/" | "?" | ":" | "@" | "&" | "="
> hex            = digit | "A" | "B" | "C" | "D" | "E" | "F" |
>                   "a" | "b" | "c" | "d" | "e" | "f"
> escape         = "%" hex hex
> unreserved     = alpha | digit | safe | extra
> xchar          = unreserved | reserved | escape
>
> (Read as: urlpath is "xchar" which, in turn, can be "unreserved",  
> which, in turn, can be "alpha", which, in turn, can be either  
> "lowalpha" or "hialpha")
>
> [1]http://tools.ietf.org/html/rfc1738
> [2]http://tools.ietf.org/html/rfc3986
>
> - --
> Cheers,
>
> Graham
>
> http://www.linkedin.com/in/ghiggins
>
> -----BEGIN PGP SIGNATURE-----
>
> iEYEARECAAYFAkw8nqUACgkQOsmLt1Nhivz/cwCgyDg4EX1f3JWV0QmbzsE/Nnky
> tvMAoP3VfEwq+Hn3xx8w252libeRVYM6iQCVAgUBTDyepVnrWVZ7aXD1AQInVAQA
> sPscOBrdXpdYszuQCmn0+iKX20U5Gx40/T5t5s0nA9RgMUOBDCsUSnfVabRybCkv
> k3DjYV/SlwPSNLa9jXUuoGHz9HzSmjFS6a8apkArCgzty8d3dBOeu03h4GMIahoj
> 489sZ19GNG6oL6H69URybPLW3Zwa/u5dpL3oeMjeEgs=
> =kvSX
> -----END PGP SIGNATURE-----

-- 
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en.

Reply via email to