Sorry but I don't know which RFC is. But this behavour supported in PHP
and ASP.NET
31.01.2013 13:15, John Benediktsson пишет:
Can you point me to the RFC that supports this change?
On Jan 30, 2013, at 5:49 PM, "Alexey V. Litvinov" <lialsoft...@mail.ru
<mailto:lialsoft...@mail.ru>> wrote:
Ok I understood what you mean. I think that having two equal-named
parameters in post-data and in url query isn't prohibited, but it's
anyway logic error. Since it's POST-request I think post-data must go
first and have priority. Url query parameters just supplement this data.
31.01.2013 12:21, John Benediktsson пишет:
Well, associative arrays return their first value:
IN: scratchpad "a" { { "a" 1 } { "b" 2 } { "a" 3 } } at .
1
Unless I misunderstand you?
On Wed, Jan 30, 2013 at 5:15 PM, Alexey V. Litvinov
<lialsoft...@mail.ru <mailto:lialsoft...@mail.ru>> wrote:
In this concrete situation I'm using jTable plugin for jQuery.
It gets from a server a list of records with AJAX request (using
ajax() from jQuery) and forms such request:
--- cut ---
Request
URL:http://localhost:8888/contracts/list?jtStartIndex=0&jtPageSize=5
Request Method:POST
Status Code:200 Document follows
Request
POST /contracts/list?jtStartIndex=0&jtPageSize=5 HTTP/1.1
Host: localhost:8888
Connection: keep-alive
Content-Length: 0
Accept: application/json, text/javascript, */*; q=0.01
Origin: http://localhost:8888
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64)
AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.56
Safari/537.17
Referer: http://localhost:8888/
Accept-Encoding: gzip,deflate,sdch
Accept-Language: ru-RU,ru;q=0.8,en-US;q=0.6,en;q=0.4
Accept-Charset: windows-1251,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 Document follows
connection: close
content-type: text/html; charset=UTF-8
date: Thu, 31 Jan 2013 00:58:38 GMT
server: Factor http.server
--- cut --
31.01.2013 8:12, John Benediktsson пишет:
Are you using a content type? For
example application/x-www-form-urlencoded?
On Wed, Jan 30, 2013 at 1:09 PM, John Benediktsson
<mrj...@gmail.com <mailto:mrj...@gmail.com>> wrote:
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
