[Date Index][Thread Index]
[Date Prev][Date Next][Thread Prev][Thread Next]
Re: I'm trying to use wml in a cgi...
- From: Jim Hebert <nospam@thanx>
- Date: Tue, 10 Feb 1998 19:30:20 -0500 (EST)
Sorry this is so long in coming...
I unset the content length (yes, it was a post) and that solved _a_
problem. It just let m find the next one. e-Perl woulc complain about not
wanting to work over a file in /tmp with the wrong extension.
On a hunch, I nuked all the CGI related environment before invoking wml,
and that solved that. Sorry, I haven't done an exhaustive investigation, I
just know one or more of those vars was the culprit, since it works now.
[L]inux has an installed base conservatively estimated at around 3 million
users.... [V]endors say that most of the top companies in the US have bought
the OS - but that few will readily admit to running their multimillion-dollar
corporations on code put together by a band of software idealists. -- _Wired_
On Sun, 8 Feb 1998, Ralf S. Engelschall wrote:
> Hello Jim Hebert, in a previous mail you wrote:
> > I've got a cgi that receives a file, writes it out to disk. One of the
> > post processing measures I want to do is pass it through wml (security
> > implications aside, for the moment -- those will be handled later).
> > One of the passes kept hanging (pass 2) but didn't when I ran the same
> > command on the command line. I broke the relevant stuff out to a shell
> > script (for readibility, in part) which I can run on the command line just
> > fine, but not in the cgi.
> > Note: the web server runs as me -- meaning it's not a permission thing.
> > When I turned off pass 2 (with -p 345678) it didn't hang.
> > Perl 5.004_04 on solaris 2.5.1 with apache 1.2.5 and CGI.pm 2.36.
> > Any thoughts?
> Hmmm... you already found that Meta-HTML is the bad guy here, so I've poked
> around its sources and found that under a CGI environment it tries to
> automatically import this. Actually the CONTENT_LENGTH variable is inspected.
> Because you say that your CGI-script received some stuff and then wants to
> process it via WML, I'm right when I'm assume that your CGI script is invoked
> via POST method?
> If yes, then the error is clear. As a workaround you had to remove or clear
> the CONTENT_LENGTH environment variable before running WML to avoid a
> re-import if it in Meta-HTML. Just add ``CONTENT_LENGTH='' in front of the WML
> call. When it then never hangs I can clear these variables in WML 1.6.1 per
> Ralf S. Engelschall
> Website META Language (WML) www.engelschall.com/sw/wml/
> Official Support Mailing List email@example.com
> Automated List Manager firstname.lastname@example.org
Website META Language (WML) www.engelschall.com/sw/wml/
Official Support Mailing List email@example.com
Automated List Manager firstname.lastname@example.org