Fabian_Frank
New Member
Hallo liebe Gemeinde.
Ich benutze auf meiner Website Joomla und würde seine Funktionen gerne mit JReview erweitern. Seitdem ich die neue Komponente installiert habe bekomme ich folgende Fehlermeldung beim Aufrufen der JReview-Funktionen.
Meine Konfiguration:
1und1 VServer
Suse 10.1 mit Plesk 8.3.0
PHP 5.1.2
Apache 2
IonCube Loader 3.1.33
Joomla! 1.5 und JReview
Auf squid-cache.org habe ich folgendes zu dem Thema gefunden.
http://wiki.squid-cache.org/SquidFaq/TroubleShooting#head-f4a45377a57a797587e0c67314da8c603f1581cc
Mir ist aber trotzdem noch nicht so ganz klar wie ich jetzt weiter vorgehen soll. Bin grad ziemlich ratlos.
Vielen Dank für die Mühe, Fabian
Ich benutze auf meiner Website Joomla und würde seine Funktionen gerne mit JReview erweitern. Seitdem ich die neue Komponente installiert habe bekomme ich folgende Fehlermeldung beim Aufrufen der JReview-Funktionen.
Code:
ERROR
The requested URL could not be retrieved
While trying to retrieve the URL: http://www.domain.de/administrator/index2.php?
The following error was encountered:
* Zero Sized Reply
Squid did not receive any data for this request.
Your cache administrator is webmaster.
Generated Thu, 12 Jun 2008 21:57:44 GMT by c02 (squid/2.6.STABLE16)
Meine Konfiguration:
1und1 VServer
Suse 10.1 mit Plesk 8.3.0
PHP 5.1.2
Apache 2
IonCube Loader 3.1.33
Joomla! 1.5 und JReview
Auf squid-cache.org habe ich folgendes zu dem Thema gefunden.
Code:
This happens when Squid makes a TCP connection to an origin server, but for some reason, the connection is closed before Squid reads any data. Depending on various factors, Squid may be able to retry the request again. If you see the "Zero Sized Reply" error message, it means that Squid was unable to retry, or that all retry attempts also failed.
What causes a connection to close prematurely? It could be a number of things, including:
* An overloaded origin server.
*
TCP implementation/interoperability bugs. See the ../SystemWeirdnesses for details.
* Race conditions with HTTP persistent connections.
* Buggy or misconfigured NAT boxes, firewalls, and load-balancers.
* Denial of service attacks.
*
Utilizing TCP blackholing on FreeBSD (check ../SystemWeirdnesses).
You may be able to use tcpdump to track down and observe the problem.
Some users believe the problem is caused by very large cookies. One user reports that his Zero Sized Reply problem went away when he told Internet Explorer to not accept third-party cookies.
Here are some things you can try to reduce the occurance of the Zero Sized Reply error:
*
Delete or rename your cookie file and configure your browser to prompt you before accepting any new cookies.
*
Disable HTTP persistent connections with the server_persistent_connections and client_persistent_connections directives.
*
Disable any advanced TCP features on the Squid system. Disable ECN on Linux with echo 0 > /proc/sys/net/ipv4/tcp_ecn/.
* Upgrade to Squid-2.5.STABLE4 or later to work around a Host header related bug in Cisco PIX HTTP inspection. The Cisco PIX firewall wrongly assumes the Host header can be found in the first packet of the request.
If this error causes serious problems for you and the above does not help, Squid developers would be happy to help you uncover the problem. However, we will require high-quality debugging information from you, such as tcpdump output, server IP addresses, operating system versions, and access.log entries with full HTTP headers.
If you want to make Squid give the Zero Sized error on demand, you can use a short C program. Simply compile and start the program on a system that doesn't already have a server running on port 80. Then try to connect to this fake server through Squid:
Mir ist aber trotzdem noch nicht so ganz klar wie ich jetzt weiter vorgehen soll. Bin grad ziemlich ratlos.
Vielen Dank für die Mühe, Fabian
Last edited by a moderator: