Actually, I can...
Originally Posted by evant
Using that document about same origin policy, I've altered my server to answered positively to the HTTP OPTIONS and the browser did follow with an HTTP POST.
So I did found how to solve this case, my next problem thought is that my server reply and the browser do not see the "data" portion of the reply but do see the header.
Even wireshark see the data and things seems to be valid yet the browser firebug and extjs do not seems to like it.
POST /ext/direct/router HTTP/1.1
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2) Gecko/20100304 Gentoo Firefox/3.6 FirePHP/0.4
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
I fail to see what firefox or extjs do not like, the header is properly separated by a \r\n the data content of the reply is valid JSON, yet when I look inside Firebug it says that it received 91 B of size in the body response yet in the "Response" tab there is nothing, it's empty.
HTTP/1.1 200 OK
Date: Mon, 08 Mar 2010 15:41:41 GMT
Any idea or suggestion?