php - method="post" enctype="text/plain" are not compatible? -

-

when use 

<form method="post" enctype="text/plain" action="proc.php">

form data can not sent proc.php file properly. why? problem? why can't use text/plain encoding post can use method?

[revised]

the answer is, because php doesn't handle (and not bug):

https://bugs.php.net/bug.php?id=33741

valid values enctype in <form> tag are:  application/x-www-form-urlencoded multipart/form-data

the first default, second 1 need when upload files.

@alohci provided explanation why php doesn't populate $_post array, store value inside variable $http_raw_post_data.

example of can go wrong text/plain enctype:

file1.php:

<form method="post" enctype="text/plain" action="file2.php"> <textarea name="input1">abc input2=def</textarea> <input name="input2" value="ghi" /> <input type="submit"> </form>

file2.php:

<?php print($http_raw_post_data); ?>

result:

input1=abc input2=def input2=ghi

no way distinguish value of input1 , input2 variables. can be

  • input1=abc\r\ninput2=def, input2=ghi, as
  • input1=abc, input2=def\r\ninput2=ghi

no such problem when using other 2 encodings mentioned before.

the difference between , post:

  • in get, variables part of url , present in url query string, therefore must url-encoded (and are, if write enctype="text/plain" - gets ignored browser; can test using wireshark sniff request packets),
  • when sending post, variables not part of url, sent last header in http request (postdata), , can choose whether want send them text/plain or application/x-www-form-urlencoded, second 1 non-ambiguous solution.

Comments

Post a Comment

Popular posts from this blog

c++ - Qt setGeometry: Unable to set geometry -

-
why? setgeometry: unable set geometry 22x22+320+145 on qwidgetwindow/'widgetclasswindow'. resulting geometry: 116x22+320+145 (frame: 8, 30, 8, 8, custom margin: 0, 0, 0, 0, minimum size: 22x22, maximum size: 16777215x16777215). the project is: project.pro qt += core gui greaterthan(qt_major_version, 4): qt += widgets target = untitled5 template = app sources += main.cpp\ widget.cpp headers += widget.h widget.h #ifndef widget_h #define widget_h #include <qwidget> class widget : public qwidget { q_object public: explicit widget(qwidget *parent = 0); ~widget(); private: }; #endif // widget_h widget.cpp #include "widget.h" #include <qvboxlayout> widget::widget(qwidget *parent) : qwidget(parent) { qvboxlayout *vlayout = new qvboxlayout(this); } widget::~widget() { } main.cpp #include "widget.h" #include <qapplication> int main(int argc, char *argv[]) { qapplication a...
Read more

python - argument must be rect style object - Pygame -

-
disclaimer: know other people on site have had error it's been in different contexts , fixes don't seem work here. hey stackoverflow, i've been making sideways space invaders game, ship follows mouse's y position stays on left, , clicking shoots bullet. enemies spawn randomly right , fly left, , objects removed once each side of screen. works fine, when tried implement collision detection see when shot hits enemy, error: typeerror: argument must rect style object. it points line "return hitbox.colliderect(target.rect)". try , work out causing made 'print' lines below see 'target.rect' (and whether proper rect object), , seemed same style shot's own rect, i'm lost why colliderect doesn't accept it. i've annotated pretty everything, sorry if it's insult intelligence should make things easier. class causes problems: class gameobject: def __init__(self, image, height, speed): self.speed = speed self.image...
Read more

How to resolve Delphi error: Incompatible types: 'PWideChar' and 'Pointer' -

-
i have piece of code delphi 7: var lprgndata: prgndata; pc: pchar; pr: prect; ... pc := @(lprgndata^.buffer[0]); in delphi xe4 gives following compile error: incompatible types: 'pwidechar' , 'pointer' how should code updated work correctly in xe4? thanks whether or not compiles depends upon setting of type-checked pointers option . have enabled option excellent decision. doing results in stricter type checking. with type-checked pointers disabled, code compile. type-checked pointers enabled, code not compile, want because code not valid. now, on types in question. defined in windows unit this: type prgndata = ^trgndata; {$externalsym _rgndata} _rgndata = record rdh: trgndataheader; buffer: array[0..0] of byte; reserved: array[0..2] of byte; end; trgndata = _rgndata; {$externalsym rgndata} rgndata = _rgndata; the benefit of using type-checked pointers compiler can tell doing not valid. knows lprgndat...
Read more