RE: No specification for querystrings and fragment identifiers

# > in the previous example, netscape3 and explorer 4 will render '&sect'
(no
# > closing ';') in the second name/value pair as the html entity '§'
# > 
# > you can work around thnx to the case sensitivity of entities
('&Section=')
# > 
# 	The correct way round this is to use the & entity to
# 	protect the & from the browser, although the HTML 
# 	reccommendations now advise form handlers which expect to
# 	be used directly like this to accept ; as a synonym for &.
# 
# 
a browser should render 'html' ... querystring syntax isnt really 'html' ?
im ok with: fds.hts?aName=fréderic
but not: fds.hts?aName=fréderic&aNameB=aValue

Received on Tuesday, 23 November 1999 08:02:13 UTC