Hi,
There are pretty useful ff extension to view JSON response:
https://addons.mozilla.org/en-US/firefox/addon/10869
Tonio
https://addons.mozilla.org/en-US/firefox/addon/10869
On May 25, 3:20 pm, Lee Bolding l...@leesbian.net wrote:
This is the correct solution.
Your browser attempts to
Action executes of file upload. If that helps to find a bug.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
symfony users group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe
My guess is your content-type.
Try keeping it text/html instead of application/json
On May 25, 10:21 am, santail nikolai.muh...@gmail.com wrote:
Action executes of file upload. If that helps to find a bug.
--~--~-~--~~~---~--~~
You received this message because
Check your headers with LiveHTTPheaders or something similar: do you
also send a content-disposition: attachment one? That's what triggers
the save as dialog. If you do, change it to inline and it should fix
it.
On Mon, May 25, 2009 at 10:09, santail nikolai.muh...@gmail.com wrote:
There is
That helps, thanks. But what the difference between these two types of
content for browser ?
On 25 май, 12:00, Leon van der Ree l...@fun4me.demon.nl wrote:
My guess is your content-type.
Try keeping it text/html instead of application/json
On May 25, 10:21 am, santail
application/json is a way to specify to the browser that what is coming is a
JSON formatted sequence of data and not html to display in the browser. If
the request wasn't initiated by an ajax request then it doesn't know how to
process properly.
2009/5/25 santail nikolai.muh...@gmail.com
That
This is the correct solution.
Your browser attempts to download the response as a file because it
doesn't know what to do with the mime type application/json
If you set the headers to text/html for testing purposes you'll see
the response as plain text in your browser
On 25 May 2009, at
