On 18/04/07, David Brown <[EMAIL PROTECTED]> wrote:
If I make the request direct to tomcat, i.e. via port 8080 its fine. Everything else delivered on the site via modjk has been ok, just this one jsp. Which leads me to think there is something in the content which is screwing with modjk. The content in question is a load of user details, but in an encrypted form so it looks like garbled text. Just one long string of garbled text. About 50k worth. Strange eh ?
Yes that is wierd, sounds like you are doing everything correctly then, I would be inclined to rebuild the rogue JSP, and testing it as you go, until it falls over again, like you say sounds like some dodgy code in the page pity it is encrypted data. Maybe thats why it works over https not http? Could you not just do a dirty fix and link to it via HTTPS? Sorry like I said im not much of an expert, but I think if you want to get to the bottom of this one you will have to play with the JSP code bit by bit, trial and error, until it falls over. You never know it might be fixed by just rebuilding the page. then again, maybe not if it already works under HTTPS...hmmm sorry........... thinking as I type again.. *Which leads me to think there is something in the content which is screwing with modjk.* I agree actually. Now i have thought about it. Mod_JK is just a connector between Apache services and Tomcat services, and presuming, as you say, that other JSP pages work fine, then I think you are right, you need to look at the page content. Hope this helps, and keep us informed of your progress. Regards Richard
_______________________________________________ Peterboro mailing list [email protected] https://mailman.lug.org.uk/mailman/listinfo/peterboro
