Order does not make sense I think. Params is associative array where the
name of param is key. We get param value by name not by order, so it
does not matters where POST-data params and where is params from url.
31.01.2013 8:09, John Benediktsson пишет:
That makes sense -- but which order should the params be in? url then
post-data or vice versa?
On Wed, Jan 30, 2013 at 1:05 PM, Алексей Литвинов <lialsoft...@mail.ru
<mailto:lialsoft...@mail.ru>> wrote:
Hi!
Does anybody knows, why when processing request parameters in http.server
in the word request-params silently ignored parameters given as part of url
when it's POST request and processed only post-data.
I think this line should look like this: { "POST" [ dup post-data>> params>> >alist [
url>> query>> >alist ] dip append ] }
It's not prohibited as far as I know to supply parameters in url (as in GET
request) when doing POST request. Or I'm wrong?
For example jTable (http://www.jtable.org) is mixing post request with
parameters in url. And PHP for example stack this parameters from url into
$_POST array too.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
<mailto:Factor-talk@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/factor-talk
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Factor-talk mailing list
Factor-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/factor-talk
