Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things
 
PerlMonks  

Re: 500 Internal server error

by sundialsvc4 (Abbot)
on Feb 06, 2014 at 21:38 UTC ( #1073769=note: print w/replies, xml ) Need Help??


in reply to 500 Internal server error

Here’s the skinny on this one:   Apache has been configured to believe that anything which is sent to <Location /cgi-bin/> corresponds to the name of a file that it should execute, in order to return to you the output from that file being executed.   (You have not specified a Handler ...)   Which is exactly what it is trying to do.   It found a file by that name at that location, but of course it is not executable.   So, Apache throws up its hands.

What you need to do is to tell Apache, say, that <Location /cgi-bin/Output/Waybill/> should cause a particular Handler, not a file in this location, to be executed.   Upon recognizing this pattern, Apache will (maybe) launch the Handler, and pass the URL-string as input to it.   That script which will be responsible for extracting whatever parameters from it and carrying-out the request.

An elementary Apache-configuration problem ... and not Perl-specific ... but, confusing nonetheless.

Replies are listed 'Best First'.
Re^2: 500 Internal server error
by Anonymous Monk on Mar 09, 2014 at 19:30 UTC
    in c++ the solution is:
    int main(){
    printf("Content-type: text/html\n\n");

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1073769]
help
Chatterbox?
[Corion]: But yes, "who started this process" is interesting information :)
[tye]: no, I really believe that "login user" was added as a fundamental bit of info about each process in order to enhance the usefulness of auditing
[Corion]: Ah - if that information is saved in a file, then you could theoretically spam that file and confuse getlogin(). So, don't use it for authentication :)
[tye]: that is what getlogin() certainly *used* to do. I don't believe that is what it certainly should do.
[davido]: /var/run/utmp is 664 i think.
[tye]: Note that my "man getlogin" says that it uses stdin when it should use /dev/tty (calling a glibc bug). But that does not appear to be the case when I test it. But maybe Perl's getlogin() is not using glibc's getlogin().
[oiskuu]: well, run a strace and see what the getlogin does for you.... As I said. SELinux probably has those security labels. But not regular linux.
[tye]: for example, read https://unix. stackexchange.com/ questions/146138/ loginuid-should-be -allowed-to-change -or-not-mutable-or -not
[tye]: I'm not using SELinux and it certainly appears to disagree with you. shrug
[tye]: Since you brought up /proc, oiskuu, I didn't see you respond to my suggestion of 'loginuid'. Does your /proc not have such?

How do I use this? | Other CB clients
Other Users?
Others avoiding work at the Monastery: (9)
As of 2017-06-23 19:44 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    How many monitors do you use while coding?















    Results (554 votes). Check out past polls.