Re^3: Help sought determining why Frontier::Client reporting too many header lines

To test to see if it is the cookies issue (I'm sure there can be multiple causes for this error -- but cookies is the first one I've found documented) you can clear cache on your browser, and turn on 'ask me every time' for cookies (and delete the existing cookies) and see how many times you get prompted for cookies. It's very possible that each user has multiple cookies (or generates multiple headers in general, if cookies aren't the culprit) that are causing the error. (or just browse your cookies afterward to see how many exist for your site after using the dept with 27 people)

If it's directly related to the number of people in that department, then I'd have to deduce that it's doing something for each of those people. It might be cookies, it might be some other type of header, but that has to be part of the reason.

Have you tried looking into the module code to see what it's trying to do? I don't have that module handy, but it might spill the beans as to what's going on, and perhaps there is some option to change the behavior to prevent this issue.

I looked on CPAN and found this bug for one of the Frontier modules. It talks about a 500 error, perhaps it's related to the one you are receiving. It's very possible that it's a bug in the module and nothing in your code can prevent it, which in case you'll either have to get it fixed yourself, or hope the author fixes it. I'd definitely examine the source of the module though to see if you can spot where the issue really is. Unfortunately I can't do that at the moment, but I will try to take a look later on if I can.

I hope that was helpful.

Comment on Re^3: Help sought determining why Frontier::Client reporting too many header lines

Replies are listed 'Best First'.
Re^4: Help sought determining why Frontier::Client reporting too many header lines by lvirden (Novice) on Jun 29, 2010 at 12:20 UTC
Thank you for your suggestions. In this particular case, the web service isn't being invoked by a browser, but a small piece of perl code, so I don't think there's any cookies involved. The specific error being generated is coming deep within Net::HTML, which is trying to read header lines and is finding more than 128 headers. I have been trying to figure out how to see the headers and xml that is being generated, but so far, I have been unsuccessful in all my attempts. The code in Frontier::Response is pretty simple and I don't see anything there that is obvious. So the problem must be deep within the XML generation process and I've just not figured out how to see what is going on there.	[reply]
Re^5: Help sought determining why Frontier::Client reporting too many header lines by sierpinski (Chaplain) on Jun 29, 2010 at 13:28 UTC
Don't forget though that the browser doesn't generate the cookie. The web server does. The browser (or you as the user) accepts it and stores it locally in the browsers computer. A piece of perl code could very easily generate cookies. Have you tried either of the previous methods I suggested to see if that is the issue? It might be a longshot, but it's an easy check, if only to rule it out as a possible cause.	[reply]
Re^6: Help sought determining why Frontier::Client reporting too many header lines by lvirden (Novice) on Jun 29, 2010 at 14:41 UTC
I looked at the bug report you mentioned. The bug report deals with Frontier::Client - but that's not the location of the bug I am seeing. The bug I am seeing appears after the method has been invoked, and in fact, after the method has returned but before the XML is returned to the caller. I have also been looking at the code. The error message is occuring down in Net::HTML which is being called by the CGI module. I'm still trying to figure out the path from Responder thru the CGI module. But so far, I've not seen anything obviously wrong, nor any simple way to get a look at the headers that the code believes are present.	[reply]