[
https://issues.apache.org/jira/browse/WICKET-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538624
]
Johan Compagner commented on WICKET-1029:
-----------------------------------------
What is invalid about that content length?
Is it to large? to little? Why do you need to disable it? That is not really
what you want to do
You should set the content length and then start to stream it. So that the
browser knows upfront
how many bytes it will get.
> Get Invalid Content-Length header returned by TCP junction server
> -----------------------------------------------------------------
>
> Key: WICKET-1029
> URL: https://issues.apache.org/jira/browse/WICKET-1029
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.2.6
> Environment: OS: Windows XP SP2
> Java 1.4.2
> IBM RAD 6.0.1
> IBM WebSeal
> Reporter: Jeroen Damen
> Assignee: Johan Compagner
> Priority: Minor
> Fix For: 1.3.0-beta5
>
>
> When I use wicket on my localhost everything goes fine.
> When I use it behind WebSeal, WebSeal gives errors on the content length
> header of the wicket javascript files.
> The error is: "Invalid Content-Length header returned by TCP junction server"
> To bypass it, I placed the following line in comment in wicket.Resource:
> response.setContentLength((int)resourceStream.length());
> Kind regards,
> Jeroen
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
