| Author | Post |
|---|
cybecom
Member
| Joined: | Sun Aug 28th, 2005 |
| Location: | |
| Posts: | 13 |
|
Posted: Tue Oct 16th, 2007 12:34 am |
|
Hi again
I've set up a sub-domain, made sure /editwrx is able to run cgi / perl scripts, beamed up an unzipped installer.cgi, made sure permissions set to 755 and installed. I've worked through setting up admin's password and a user but when I login (tried as admin), I get what is probably the resulting page but with graphics crossed out. A look at the error log yields the following for each of the graphic files:
[Tue Oct 16 02:17:52 2007] [error] [client ip.ip.ip.ip] Premature end of script headers: /hsphere/local/home/username/test.domain.net.au/editwrx/ikons/filename.gif
Scripts can obviously run because they've managed to work until this point. Any ideas?
Regards
Michelle
|
cybecom
Member
| Joined: | Sun Aug 28th, 2005 |
| Location: | |
| Posts: | 13 |
|
Posted: Tue Oct 16th, 2007 12:39 am |
|
One more thing.... my sub-domain hasn't shown up in the DNS yet so I'm using the server's temporary URL to access editWrx (and I used that when I installed too).
Michelle
|
Keith
Moderator
| Joined: | Fri Apr 8th, 2005 |
| Location: | |
| Posts: | 578 |
|
Posted: Tue Oct 16th, 2007 01:10 am |
|
/hsphere/local/home/username/test.domain.net.au/editwrx/ikons/filename.gif
It appears that it thinks ikons/filename.gif is an executable script?!? In fact, I just tried http://test.domain.net.au/editwrx/ikons/bb.gif and it indeed does return a 500 error instead of the image. It also thinks http://test.domain.net.au/editwrx/library/data/config.txt is an executable.
Whatever you did to "made sure /editwrx is able to run cgi / perl scripts" looks like it turned /editwrx into a scriptAlias directory. On Apache a scriptAlias directory can contain only executables, so it will treat all files in that directory as an executable. That step needs to be undone.
I put a test.txt at http://test.domain.net.au/cgi-bin/test.txt and it returns a 500 error also, which is to be expected since a cgi-bin is by definition a scriptAlias directory.
On your server you do not really need to do anything special to be able to run a cgi script anywhere in the domain. The entire domain has an ExecCGI AddHandler so scripts can actually run anywhere. In fact, I just created http://test.domain.net.au/bingo/env.cgi and it needed only 0755 permissions to run.
The cgi-bin (scriptAlias) is an obsolete concept that should not even be in a domain by default. They were used back in the pre-1996 days when Apache had no support for file extensions and using a dedicated directory was the only way to tell Apache which files to try to execute rather than just serve raw.
Just undo that step that "made sure /editwrx is able to run cgi / perl scripts" and you should be ready to rock 'n roll.
|
cybecom
Member
| Joined: | Sun Aug 28th, 2005 |
| Location: | |
| Posts: | 13 |
|
Posted: Tue Oct 16th, 2007 01:42 am |
|
Hi again
FIXED!!!! Yes - I reversed that step of adding editwrx as a cgi-bin folder (although the system must be doing that SCRIPTAlias thingo - obviously me not understanding what I am really doing) and all seems to be working fine now.
Thank you.
Cheers
Michelle
|
Current time is 05:05 pm | |
|
