 |
 |
 |
 |
|
|
Date: 07/31/00
- Next message: Bug Database: "[PHP-DEV] PHP 4.0 Bug #5878 Updated: Problem to open a file?"
- Previous message: waldschrott: "Re: [PHP-DEV] PHP 4.0 Bug #5823: PHP assumes MySQL unix socket is always available"
- In reply to: Ragnar Kjørstad: "[PHP-DEV] Re: PHP 4.0 Bug #4439 Updated: PHP doesn't handle content-transfer-encoding header on form-based file upload"
- Next in thread: Sascha Schumann: "Re: [PHP-DEV] Re: PHP 4.0 Bug #4439 Updated: PHP doesn't handle content-transfer-encoding header on form-based file upload"
- Reply: Sascha Schumann: "Re: [PHP-DEV] Re: PHP 4.0 Bug #4439 Updated: PHP doesn't handle content-transfer-encoding header on form-based file upload"
- Reply: Ragnar Kjørstad: "Re: [PHP-DEV] Re: PHP 4.0 Bug #4439 Updated: PHP doesn't handle content-transfer-encoding header on form-based file upload"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Whatever is sending that is not MIME compliant. Double quotes are not
optional in the Content-Disposition header. ie. it should be:
Content-Disposition: form-data; name="input"
-Rasmus
On Mon, 31 Jul 2000, [iso-8859-1] Ragnar Kjørstad wrote:
> On Sun, Jul 30, 2000 at 12:07:01PM -0000, Bug Database wrote:
> > ID: 4439
> > Updated by: zak
> > Reported By: php <email protected>
> > Status: Feedback
> > Bug Type: Scripting Engine problem
> > Assigned To:
> > Comments:
> >
> > Is this a PHP issue or a cURL issue - does anyone want to test this out?
> >
> > Full Bug description available at: http://bugs.php.net/?id=4439
>
> Sorry for not using the webinterface - I don't remember my password.
>
> According the the curl developer, it was a php-bug. I also detected a
> simular problem (the result is different, but they both seem to be
> caused by invalid assumptions in the parsing-code).
>
> When I send the following http request: (only relevant part)
> POST /login.php HTTP/1.0
> User-Agent: Lynx/2.8.3dev.18 libwww-FM/2.14
> Content-type: multipart/form-data; boundary=xnyLAaB03X
> Content-length: 610
>
> --xnyLAaB03X
> Content-Disposition: form-data; name=input
> Content-Type: text/plain; charset=iso-8859-1
>
> yes
> --xnyLAaB03X
> Content-Disposition: form-data; name=next
> Content-Type: text/plain; charset=iso-8859-1
>
>
> --xnyLAaB03X
> Content-Disposition: form-data; name=brukarnamn
> Content-Type: text/plain; charset=iso-8859-1
>
> eurofoto <email protected>
> --xnyLAaB03X--
>
> php produces the error:
> File upload error - no name component in content disposition in Unknown on line 0
>
>
>
-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: Bug Database: "[PHP-DEV] PHP 4.0 Bug #5878 Updated: Problem to open a file?"
- Previous message: waldschrott: "Re: [PHP-DEV] PHP 4.0 Bug #5823: PHP assumes MySQL unix socket is always available"
- In reply to: Ragnar Kjørstad: "[PHP-DEV] Re: PHP 4.0 Bug #4439 Updated: PHP doesn't handle content-transfer-encoding header on form-based file upload"
- Next in thread: Sascha Schumann: "Re: [PHP-DEV] Re: PHP 4.0 Bug #4439 Updated: PHP doesn't handle content-transfer-encoding header on form-based file upload"
- Reply: Sascha Schumann: "Re: [PHP-DEV] Re: PHP 4.0 Bug #4439 Updated: PHP doesn't handle content-transfer-encoding header on form-based file upload"
- Reply: Ragnar Kjørstad: "Re: [PHP-DEV] Re: PHP 4.0 Bug #4439 Updated: PHP doesn't handle content-transfer-encoding header on form-based file upload"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]