Problems to open cgi-bin/gm.cgi in firefox

[buppie]

Hi,

Suddenly I get a strange problem when I try'd to open www.devrije.nl/cgi-bin/gm.cgi in Firefox.
I get only the html code from the first page of the blog without the content.
In Explorer I have no problems at all.

The console in firefox tells me that there's a javascript problem
after I click javascript:http//www.devrije.nl/....... I get the next message what you can see in the picture. Click....
img187.imageshack.us/my.php?image=fireproblemvv2.jpg
Someone knows how to solve this, thanks.

[coldstone]

This is not a javascript error, rather its how picky a browser is when displaying a page. IE (and other browsers such as Safari) are happy to render a page as html by default. I noticed when viewing your page, that the first line in the upper left corner is "Content-type: text/html". This makes me suspect that an extra return or newline is being printed before the content type is, which Firefox is being picky about. It is assuming the page is just plain text.

It looks like you are using v1.3 (which is before my time). Have you made any changes to it at all?

[buppie]

I didn't change anything in Greymatter, and yes I use version 1.3.
I'm running this version now for 2 years and never have had any problems at all. 2 days ago this problem occur in Firefox, maybe it have something to do with upgrades from the browser itself.

But firefox has to open gm.cgi and that's a script so far as I can see.
Maybe it's has something to do with this line in gm.cgi

# ----------------------------------------
# gathering the input & checking for login
# ----------------------------------------

print "Content-type: text/html\n\n";

$authorIP = $ENV{'REMOTE_ADDR'};

$logindeletednotice = "";

But I'm not so good in scripting. I'm afraid that this problem also will occur in IE over a while, that's why I want a solution.

Thanks for answering, I do hope someone knows a simple answer to this problem.

[coldstone]

This should be a simple solution, but I found a download of GM 1.3 and couldn't see a simple solution. In fact when I setup the files for 1.3 I could not duplicate this issue.

The only issue I encountered was that I had to convert the files to ascii to get rid of window style file endings, but this isn't a problem you would see happen suddenly.

What platform is your site hosted on (Unix or Winows)? You might try re-uploading the gm.cgi file to your site (make a backup of the old version first) and see if that helps.

Otherwise, if you copy your gm.cgi file to gm.txt and post a link to it, I could look and see if there is something specific with you file.

[buppie]

Thanks Coldstone, but I did find a solution for my problems, I removed the line print "Content-type: text/html\n\n"; in cgi-bin/gm.cgi and that solved the problem. Your first post in this thread helped me a lot to let my brain working to the good direction.

Thanks again.

[buppie]

A well the problem is bigger then I thought it would be, my hostingprvider upgraded Perl to version 5.8.6.811.
This is the providers solution:
The last update was nessesary for the safety of our servers. Now perl have chanced the the way it work up with the headers in ISAPI mode.
That's why we put perl in CGI mode and the working stays the same
But you have to change all the paths who pointed to *.cgi files in the script files.
You can make a variable like this
$cgibin_path = "D:/www/devrije.nl/www/cgi-bin/";
require $cgibin_path ."gm-library.cgi";
And ofcourse all the other paths..................

Well you see that I have my hands in my hair, I'm not a programmer.
Maybe there is a solution to upgrade GM to 1.7.1, but would it help?
I made a post in installation issues with a problem with version 1.7.1.

O I forget to tell my website is becom totally usseles because of the perl update, I can't log anymore.

Thanks.

[coldstone]

I don't think an upgrade to 1.7.1 will fix anything, but you can try.

Unfortunately, I think this will be a large change to your scripts, it sounds like the perl won't allow relative paths. Unfortunately GreyMatter was setup with a lot of file access, and the last two versions of GreyMatter try to address this, but its a big task and the work is still ongoing.

I can read u p on ISAPI mode, but right now I am in the dark too.