What is the difference between URL encoding, URL rewriting, HTML escaping, and entity encoding?
URL Encoding is a process of transforming user input to a CGI form so it is fit for travel across the network — basically, stripping spaces and punctuation and replacing with escape characters. URL Decoding is the reverse process. To perform these operations, call java.net.URLEncoder.encode() and java.net.URLDecoder.decode() (the latter was (finally!) added to JDK 1.2, aka Java 2). Example: changing “We’re #1!” into “We%27re+%231%21” URL Rewriting is a technique for saving state information on the user’s browser between page hits. It’s sort of like cookies, only the information gets stored inside the URL, as an additional parameter. The HttpSession API, which is part of the Servlet API, sometimes uses URL Rewriting when cookies are unavailable. Example: changing into (or whatever the actual syntax is; I forget offhand) (Unfortunately, the method in the Servlet API for doing URL rewriting for session manage
Related Questions
- Is this question about encoding URL GET parameters, i.e. changing spaces to +, or about encoding data to be displayed on an HTML page that may have <,>, and & in it?
- What is the difference between URL encoding, URL rewriting, HTML escaping, and entity encoding?
- Does webserver 6.1 support toggling of strictly enforced url encoding?
