encoding - What is the point of Tomcat's setting URIEncoding? -


in apache tomcat, parameter uriencoding tells tomcat how interpret incoming uris:

uriencoding

this specifies character encoding used decode uri bytes, after %xx decoding url. if not specified, iso-8859-1 used.

apache tomcat 7 - http connector

however, explained example in what proper way url encode unicode characters? , non-ascii characters in uris encoded in utf-8, following current standards (rfc 3986 , 3987).

so:

  • why there setting mandated standard?
  • why default different standard mandates? (iso-8859-1 instead of utf-8)

is because tomcat setting predates standard, , retained backwards compatibility? or there situation value different utf-8 makes sense?

the description of parameter uriencoding in tomcat 8 - apache tomcat 8 - http connector:

this specifies character encoding used decode uri bytes, after %xx decoding url. if not specified, utf-8 used unless org.apache.catalina.strict_servlet_compliance system property set true in case iso-8859-1 used.

thus description changed of apache tomcat 7. default value of org.apache.catalina.strict_servlet_compliance false apache tomcat 8. utf-8 default value of uriencoding apache tomcat 8, means tomcat follows standard (and common usage).

as why tomcat used iso 8859-1 default uri encoding until tomcat 7:

that seems because tomcat devevelopers believed servlet specification requires (as name of setting strict_servlet_compliance indicates).

as matter of fact, servlet spec not explicitly mention uri encoding in version. does, however, mention post data must parsed iso 8859-1 if content-type http header not specify encoding via charset (servlet specification v2.5, "request data encoding"). apparently interpreted mean query parameters (and whole uri) should decoded iso 8859-1 default.

the root problem arguably servlet specification not specify default encoding use decoding uris, let alone way change encoding. in turn because uri spec did not allow non-ascii characters in uris - standardized introducing iris, see rfc 3987 january 2005. therefore every servlet container had come own default value , configuration parameter, such uriencoding in apache tomcat.

these 2 problems have been reported bugs against servlet specification:

maybe servlet specification amended 1 day...


Comments

Post a Comment

Popular posts from this blog

javascript - jQuery: Add class depending on URL in the best way -

i have html progress meter: <div class="col-md-3" style="margin-left: -20px;"> <div class="progress-pos active" id="progess-1"> <div class="progress-pos-inner"> login </div> </div> </div> <div class="col-md-3 progress-pos-container"> <div class="progress-pos" id="progess-2"> <div class="progress-pos-inner"> scan items </div> </div> </div> <div class="col-md-3 progress-pos-container"> <div class="progress-pos" id="progess-3"> <div class="progress-pos-inner"> confirm address </div> </div> </div> <div class="col-md-3 progress-pos-container"> <div class="progress-pos" id="progess-4"> <div class="progress-pos-in...
Read more

caching - How to check if a url path exists in the service worker cache -

i need check if particular url path exists in service worker cache. example, suppose url is: /myserviceworker/service?a=110&b=70 this url exists in cache, there many of them different values of , b. now, suppose want refresh of these urls, how can that? i want know how access key values service worker cache. if know key, plan follows: var url = new url(key); if(url.pathname === "\/myserviceworker/service") refetch key but not sure how cache key , in format is. mean, string or url? cache api has match() method returns promise resolving in response object if match or undefined if no match exists. second parameter object can specify ignoresearch not take account url parameters. the ignoresearch option supported firefox ( chrome status here ). in other hand, retrieve cache entries, can use keys() method.
Read more

Redirect to a HTTPS version using .htaccess -

i need modify .htaccess file redirect urls https version without "www". http://example.com --> https://example.com http://www.example.com --> https://example.com https://www.example.com --> https://example.com this how .htaccess file looks like: rewriteengine on rewritecond %{request_filename} !-d rewritecond %{request_filename} !-f rewriterule ^(.*)$ redirect.php?id=$1&page=$2 [qsa,l] what modifications need make .htaccess in order forward https without "www"? it depends on doing current code. looks file called redirect trying display php page seo friendly url. think might confusing people. anyway, need , force https without www, need 1 more rule above. also second rule needs two capture groups in rewriterule test string because wanting 2 different values using $1 , $2 references. rewriteengine on #rediect www non www and/or http https --- combinations. rewritecond %{http_host} !^example\.com [nc,or] rewritecond %{https} !^...
Read more