products forums blog support careers about
  History | Log In     View a printable version of the current page.  
PRO USERS, to ensure 'PRIORITY SUPPORT' make sure that your ASAP account is "tagged" when you file the request. Click here for instructions on how to tag your account.
Issue Details (XML | Word | Printable)

Key: STU-2907
Type: Bug Bug
Status: Reviewed Reviewed
Priority: Unprioritized Unprioritized
Assignee: Sandip Chitale
Reporter: Nathan L Smith
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Aptana Studio

Excessive Header Length Causes Apache 500

Created: 14/Nov/08 01:06 PM   Updated: 21/May/09 08:02 PM
Component/s: Jaxer Support
Affects Version/s: Aptana Studio 1.2
Fix Version/s: Bandini Release

Environment: Ubuntu Server 8.04, Apache 2.2.8

Impact on Workflow: Average
Specific Build Number: 4147
Studio Install Type: N/A
Operating System: Ubuntu
Participants: John Zhang, Nathan L Smith and Sandip Chitale


 Description  « Hide
This is re-posted from http://forums.aptana.com/viewtopic.php?t=7208:

This code:

<script runat="server">
Jaxer.response.setClientFramework(null);
Jaxer.response.headers["Content-Type"] = "text/html";
var h = Jaxer.response.headers;
var s = [];
s.length = 3926;
h['X-TEST-1'] = s;
</script>

runs fine. It just sets a header to a string of 3,925 commas. However, if you add:

h['X-TEST-2'] = s;

A second time, just before the closing script tag, I get a 500 from Apache, and this in my server error log:

[Mon Nov 10 21:08:43 2008] [warn] mod_jaxer: invalid data type (\x02) received, while expecting a body (4)
[Mon Nov 10 21:08:43 2008] [warn] [client 71.213.224.23] (500)Unknown error 500: mod_jaxer: parse response body failed

If I change 3926 to 3925, both headers get sent.

If I repeat this process for smaller lengths with more headers, I get the same error everytime it's around 7500-8000 total characters. Is there a limit to the total header length sent by Apache or Jaxer? I couldn't find anything by googling.

I found this while working on this: http://forums.aptana.com/viewtopic.php?p=26057

Davey said: "spoke with one of the server devs, and he said to open a ticket for the header length issue. It is a limit in the jaxer protocol, that we should be able to extend."



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
John Zhang - 19/Nov/08 04:30 PM
Jetty connector appears having the same issue.
Basically, when the response header content is large, Jaxer will send it back in multiple blocks. While reading/parsing the headers, the connector must process all header blocks.