On 3/19/07, Zdenek Machac <machac@ics.muni.cz> wrote:

Hi,

yes content length is not correct. We want to use encoding iso-8859-2 to
  pages in XWiki. I change encoding config in:

velocity.properties:

input.encoding=ISO-8859-2
output.encoding=ISO-8859-2

web.xml:

   <filter>
     <filter-name>Set Character Encoding</filter-name>

<filter-class>com.xpn.xwiki.web.SetCharacterEncodingFilter</filter-class>
     <init-param>
       <param-name>encoding</param-name>
       <param-value>ISO-8859-2</param-value>
     </init-param>
   </filter>

Where is mistake? Other config files must be changed? Search for
iso-8859-2 or ISO-8859-2 text in files are only web.xml,
velocity.properties (result without xml files with encoding on first
line and wml.vm, s5* templates)

Thanks

Zdenek Machac

Sergiu Dumitriu napsal(a):
> Hi,
>
> The content-length HTTP header is not correct. This is caused by an
> encoding misconfiguration.
>
> Sergiu
>
> On 3/19/07, *Zdenek Machac* < machac@ics.muni.cz
> <mailto:machac@ics.muni.cz>> wrote:
>
>     Hallo,
>
>     I have problem with loading pages from XWiki (in Glassfish application
>     server). Loading static files is fast (.js, .css, pictures in
>     millisecond). Dynamic pages are showed fast too, but browsers (Firefox,
>     IE, Opera) are waiting to end loading for 30 seconds. It terrible to
>     wait 30 seconds to show WYSIWYG editor (because onLoad event).
>
>     I tested with web tools then complete page is loaded for about 1 seconds
>       (all js,css,pictures and ending html tag) but browsers are waiting
>     (and looks like loading). It not only my problem but all computers in
>     all department. I tested disabling cache and stats but no positive
>     result.
>
>     Has everybody same problem or experience with Glassfish?
>
>     Thanks for any ideas.
>
>     Zdenek Machac
>