in reply to Re: enctype problem in CGI
in thread enctype problem in CGI

merlyn

I checked the Change.log and didn't spot any reference to this.

Don't understand ...

This shouldn't be a problem for conforming CGI server interpreters (such as CGI.pm itself)

What does this mean ?

Thanks

Replies are listed 'Best First'.
Re^3: enctype problem in CGI
by merlyn (Sage) on Mar 27, 2005 at 01:02 UTC
    What does this mean ?
    This means, why do you care? {grin} As long as you're generating the form with CGI.pm, and also interpreting the form with CGI.pm, and using a modern browser, this all works nicely together.

    If you're doing something dumb like writing a hand-rolled CGI interpreter to handle the incoming form, this breaks it. Oh well. Shouldn't be doing that, anyway.

    -- Randal L. Schwartz, Perl hacker
    Be sure to read my standard disclaimer if this is a reply.

      Ok - with you on that.

      Doesn't explain:

      the 2 enctype entries in the FORM tag

      the inability to override the default

      The lack of reference on the Changes.log

      And it is being handled by a dumb hand-rolled CGI interpreter - which I don't think is a fair scapegoat for this issue.

        I disagree--the underlying problem here is the dumb, hand-rolled CGI interpreter. Why are you using it?

        =cut
        --Brent Dax
        There is no sig.