Women in Technology

Hear us Roar



Article:
  Two Servlet Filters Every Web Application Should Have
Subject:   MAJOR bug in compression filter for non-US webapps
Date:   2004-01-07 10:03:20
From:   anonymous2
Response to: MAJOR bug in compression filter for non-US webapps

I just installed the latest version of this code to get compression. However it seems that there is still an issue with i18n.
Before putting the filter, Mozilla displayed my app in english and IE in french.


With compression, both browsers display my messages in english... Is this another attribute that should be captured and transfered but is not?


D. de Waleffe

Full Threads Oldest First

Showing messages 1 through 2 of 2.

  • MAJOR bug in compression filter for non-US webapps
    2004-01-07 18:54:34  jfalkner [View]

    How are you doing i18n detection in your web app? If it isn't using something the cache filter relies on (i.e. standard i18n headers) it won't work with the cache filter. However, it should be a relatively easy fix to modify the cache filter to work with any i18n scheme you are using -- take advantage of the source-code!
    • MAJOR bug in compression filter for non-US webapps
      2004-01-08 02:00:40  anonymous2 [View]

      I rely on struts to do this....

      However I just observed that the behaviour I mentionned depends on the server I'am using...
      Using one instance (the local tomcat), I get Mozilla-en, IE-fr. Using the other instance on another machine I have (same code) Mozilla-en,IE-en...

      So it must come from something else than the compression code... Sorry for this thought...
      D. de Waleffe