Topic: enabling cgi-bin in ibays E/S 4.0.1

[Tim Bynum]

I posted this on the general posting but did not get an answer.  Has anyone experienced this?

I have a virtual domain using an ibay. The vitual doamin works fine but I cannot get the cgi-bin enabled. I am using E-Smith 4.0.1 and I followed the direction in the update post.

>CGI scripts are disabled by default in i-bays. As CGI scripts run on the e-smith >server, they should be carefully checked before enabling.
>
>To enable CGI scripts for a particular i-bay, follow these steps:
>
>Copy the script into the cgi-bin directory
>Add execute permission to the script by executing the following command: >chmod +x script
>Run the following commands (substituting the i-bay name for i-bay):
>/sbin/e-smith/db accounts setprop i-bay CgiBin enabled
>/sbin/e-smith/signal-event console-save

but I still get a "The page cannot be found" message when I try to access "http://www.mydomain.xxx/cgi-bin/myscript".

I know it is not a problem with the script because it works fine in the primary web site.

Can anyone help?

[Gordon Rowell]

Tim Bynum wrote:
> [....]
> but I still get a "The page cannot be found" message when I
> try to access "http://www.mydomain.xxx/cgi-bin/myscript".
> [...]

Try:

http://www.mydomain.xxx/I-BAY-NAME/cgi-bin/myscript

Gordon

[Tim Bynum]

I have a virtual domain (www.mydomain.xxx) that points to the ibay.  The html for the ibay come up fine when I refer to www.mydomain.xxx.  I just cannot access the cgi-bin.

I tried "http://www.mydomain.xxx/cgi-bin/myscript" but I got "404 Not Found".

Tim

[Gordon Rowell]

Tim Bynum wrote:
>
> I have a virtual domain (www.mydomain.xxx) that points to the
> ibay.  The html for the ibay come up fine when I refer to
> www.mydomain.xxx.  I just cannot access the cgi-bin.
>
> I tried "http://www.mydomain.xxx/cgi-bin/myscript" but I got
> "404 Not Found".

Hi Tim,

The cgi-bin ScriptAlias was accidentally disabled in 4.0.1 and is (uninentionally) not affected by the CgiBin property for the i-bay. We have fixed this
in our latest development stream and will back-port it to 4.0.1 soon.

Thanks for the details, and sorry for misunderstanding your problem

Gordon