diff options
| author | http://jmtd.livejournal.com/ <http://jmtd.livejournal.com/@web> | 2009-10-15 12:41:02 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2009-10-15 12:41:02 -0400 |
| commit | 3d268733a31fb3e8a27745a37ac12bf422acb3d8 (patch) | |
| tree | 23141d6ed9b358c2151ac779443280d7a03108b4 /doc/forum/Ikiwiki_CGI_not_working_on_my_server__44___and_it__39__s_a_binary_file__63__.mdwn | |
| parent | 4c3264cd46e48e3b3327e5b02689ad2eba6a53b9 (diff) | |
| download | ikiwiki-3d268733a31fb3e8a27745a37ac12bf422acb3d8.tar ikiwiki-3d268733a31fb3e8a27745a37ac12bf422acb3d8.tar.gz | |
why the wrapper is a binary
Diffstat (limited to 'doc/forum/Ikiwiki_CGI_not_working_on_my_server__44___and_it__39__s_a_binary_file__63__.mdwn')
| -rw-r--r-- | doc/forum/Ikiwiki_CGI_not_working_on_my_server__44___and_it__39__s_a_binary_file__63__.mdwn | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/forum/Ikiwiki_CGI_not_working_on_my_server__44___and_it__39__s_a_binary_file__63__.mdwn b/doc/forum/Ikiwiki_CGI_not_working_on_my_server__44___and_it__39__s_a_binary_file__63__.mdwn index a3cb0ae0b..dc274c5b2 100644 --- a/doc/forum/Ikiwiki_CGI_not_working_on_my_server__44___and_it__39__s_a_binary_file__63__.mdwn +++ b/doc/forum/Ikiwiki_CGI_not_working_on_my_server__44___and_it__39__s_a_binary_file__63__.mdwn @@ -3,3 +3,10 @@ Hey, trying to get ikiwiki working on my account on a shared webserver. Actually My first thought was that this is a Perl CGI and I would need to change the shebang to point to the unusual location of Perl on this server, it's at /usr/pkg/bin/perl. But when I looked at ikiwiki.cgi I found it was a binary file. Why is it a binary? And what can I do about this error? + +> It's a binary because it's SUID, so that it has permission to write to the ikiwiki repository. See [[security]], under 'suid wrappers', for more on that. +> +> As to why you get 'premature end of script headers', that suggests there is a problem running +> the script (and there is output occurring before the HTTP headers are printed). Do you have access +> to the webserver logs for your host? They might contain some clues. Are you sure that the webserver +> is setup for CGI properly? -- [[Jon]] |