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

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.

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

Replies are listed 'Best First'.
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]