You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2009/02/02 08:25:59 UTC
[jira] Closed: (WICKET-1029) Get Invalid Content-Length header
returned by TCP junction server
[ https://issues.apache.org/jira/browse/WICKET-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg closed WICKET-1029.
---------------------------------
Resolution: Fixed
> 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.5-M1
>
>
> 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.