Menu

#390 Content Encoding Error

Latest_version
open
nobody
None
5
2013-09-09
2013-09-07
No

SGS: 0.745
SGS Lang: English
PHP: PHP 5.3.13
Dbase: MySQL: 5.0.91
Server OS: Linux boscustweb1805.eigbox.net 3.2.44 #1 SMP Tue May 14 15:31:28 EDT 2013 x86_6
Webserver: Apache/2 (from SERVER_SOFTWARE ... apache_get_info() is disabled on my host)
Browser: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:23.0) Gecko/20100101 Firefox/23.0 running on Linux Mint 15(olivia686) Cinnamon 1.8.8
Role: Looking to adopt for group use or adapt; user with some programming knowledge

Problem: I apparently completed a successful install, but on trying to start /sgs/bin/index.php it fails with: 'Content Encoding Error - The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression'. System won't proceed past this. Using Google Chrome as browser, I have the same problem, error message is slightly different.

I've checked all php settings referred to in installation instructions but can't see anything. I tried adding zlib to accept-encoding in the browser, just in case, but still same. Screen Shots from Firefox and Chrome are attached, together with my phpinfo(). Below are the page headers. Same problem whether I use http:// or https://. Found a similar item in forum on google groups, but it had no response and was from over 2 years ago.

I'm on a shared hosting server. I don't have MySql admin access, but database has been created fine, and otherwise I can't see anything obvious. But it probably is!

What can I try?

Kind Regards,
JW

Header traffic:

GET /sgs/bin/index.php HTTP/1.1
Host: www.havenventures.com
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:23.0) Gecko/20100101 Firefox/23.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8
Accept-Language: en-gb,en-us;q=0.8,en;q=0.6,es-uy;q=0.4,pt-br;q=0.2
Accept-Encoding: zlib, gzip, deflate
Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache

HTTP/1.1 200 OK
Date: Sat, 07 Sep 2013 19:33:29 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 5413
Connection: keep-alive
Server: Apache/2
X-Powered-By: PHP/5.3.13
Set-Cookie: d85dd092bb8e334c5db0e78d9c81cbaa=53e1ef395f08f31081ca020b36591d04; expires=Mon, 07-Oct-2013 19:33:29 GMT; path=/; secure; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT, 0
Cache-Control: private, max-age=1, must-revalidate, private, pre-check=0, post-check=0, max-age=0
Pragma: private, no-cache
Etag: "SGS22757631099061"
Content-Encoding: gzip

3 Attachments

Discussion

  • Jonathan Wood

    Jonathan Wood - 2013-09-08

    Hold the front page; just got a (delayed) post on the google forum from Faruq Hasan which allowed me to fix this by turning off compression (editing config.php and setting CORE_COMPRESS_OUTPUT to false). I can now log in and experiment!

    If there is something I can do to help further track down the source of the conflict in settings on this virtual host setup, please let me know.

    For reference other issues I've come across so far:
    - installation did not work until I changed all directory and file permissions to 755. (777 on the directory caused suexec security policy exception).
    - now on the landing page I'm getting a couple of wobbles because of PHP error_reporting: Message appears on the top of the Landing page (reference to undefined $_SERVER['QUERY_STRING']; and intermittently - a seemingly more serious failure - when a JSON parse falls over because of a similar reference to undefined index "SERVER_ADDR" which creates an error popup, though I seem to be able to continue after acknowledging it.

    if you want more on either of these, please let me know.

    Kind Regards
    JW

     
  • Jonathan Wood

    Jonathan Wood - 2013-09-09

    Thomas, FYI, my CGI error logs are also shows many "PHP Deprecated: Directive 'register_long_arrays' is deprecated in PHP 5.3 and greater in Unknown on line 0 " warnings from virtually every module. And I've had to change directory and file permissions to 755 in the admin.change_setup_options, as new directories created with 777 and modules with 644 continue to create security policy exceptions (evidently a reflection of the shared hosting setup).Apart from that, everything is smooth. This is a major work; congratulations.

     

Log in to post a comment.