|
From: <php...@li...> - 2007-08-04 16:29:57
|
Hi, > It appears that the problem I was having with fread() errors (which, by the way, Jost, I > couldn't find any errors in the logs. Where would I find this log? Tomcat should report the > error, shouldn't it?) yes. -- The php.java.bridge.default_log_level is 3, which means that exceptions and errors are logged to the tomcat error log (usually called logs/NODENAME_date). > has to do with a JavaScript function interfering with Java. I guess Can you please open a problem report (please use http://sourceforge.net/tracker/?func=add&group_id=117793&atid=679233), set the log level to 5 and attach the log there? Maybe it is possible to also attach the request headers, obtained by adding the following line to Java.inc (line 265 in the current code http://php-java-bridge.cvs.sourceforge.net/php-java-bridge/php-java-bridge/server/META-INF/java/Protocol.inc?revision=1.11&view=markup): echo "request header::$str<br>\n"; I suspect that PHP could not parse the request headers correctly, probably because the back end has sent both, the PHP cookie and the JAVA cookie in an unusual way. -- I could not reproduce this, just a guess. They should be separated by a "; " and the value should be properly URLEncoded. Basically the bridge simply forwards the request URL to the back-end. I think what happened is that Java.inc has sent a garbage URL to tomcat and tomcat responded with a HTML error message. The bridge failed to detect the error condition and tried to parse the HTML error as a PHP/Java Bridge protocol response. > That is what appears is happening with the setCookie function that exists in java.inc as well as Yes, setCookie could be smarter. It should detect if the value is properly URLEncoded for example. I will check this. Regards, Jost Boekemeier __________________________________ Alles was der Gesundheit und Entspannung dient. BE A BETTER MEDIZINMANN! www.yahoo.de/clever |