Re: [cobalt-users] Failure to conform to CGI standards ???

["Michael D. Schleif" <mds-resource@xxxxxxxxxxxx>]

flash22@xxxxxxx wrote:
> 
> yes, you can disable cgiwrap in user web space via .htaccess (depending on
> machine) and you don't have to modify system-wide config
> 
> put this in a .htaccess file on main site and user sub site..it bypasses
> cgiwrapper by fooling the server into using mime handlers , you might need
> to alias scriptdir tho...offhand i forget if ScriptAlias works in
> .htaccess
> 
> ---
> #put in .htaccess
> AddType application/x-httpd-cgi .cgx
> ---
> rename your cgi to something.cgx (for testing)

 #1 <http://www.helices.org/~helices/tmp/test5.cgx>
 #2 <http://www.helices.org/~helices/tmp/test5.cgx?tmp=pictures>
 #3 <http://www.helices.org/~helices/tmp/test5.cgx/tmp/pictures>
 #4
<http://www.helices.org/~helices/tmp/test5.cgx/tmp/pictures?tmp=pictures>

Yes, I believe that this is now the correct behavior!  Even
$DOCUMENT_ROOT shows up, again ;>

So, please, explain to me what is this demonstrating?  What is the Root
Cause?  CGIWrap?  httpd.conf?

Can I use this as-is?  What is the penalty, if I elect to use this
method?

Thank you -- I am getting closer and can effect change in the right
direction; therefore, I know that there is a solution to this problem.

However, I am not yet clear as to the source of the problem.  Who needs
to take ownership of this problem?  CGIWrap?  Cobalt's httpd.conf
coders?

What do you think?

-- 

Best Regards,

mds
mds resource
888.250.3987

"Dare to fix things before they break . . . "

"Our capacity for understanding is inversely proportional to how much we
think we know.  The more I know, the more I know I don't know . . . "