Submitting a form seems to be mis-interpreting the response type

[bee]

Hi Guys,

I am facing the same problem even if I set content type as text/html. below is my json script

begin
update image_gallary set picture = :body where image_id = :v_image_id;
:success := 'true';
end; 

It throws me below error as:

• Uncaught Ext.Error: You're trying to decode an invalid JSON String: <pre style="word-wrap: break-word; white-space: pre-wrap;">{"success":"true"}</pre>

?Please let me know how to resolve this. One more thing is that it store image at server place but may be return response is wrongly interpreted. But not getting clue how to solve this . I am not getting message alert of success.

[skirtle]

Judging by that error message it seems that the JSON is coming back wrapped in HTML pre tags. Check the response in Firebug to confirm. If this is the case then your problem is with your server, not ExtJS.

[bee]

Ok. Do we have any other work arround for this ? My data is stored in the database for that image id, but my problem is I am not getting alert box for "successfully processed". Can we do any other way to display that message as least.

[skirtle]

How are you checking that the content-type of the response is text/html?

Are you seeing this problem in different browsers?

Could you post the request and response headers for the request, as seen in Firebug or Chrome?

[bee]

Please find screen shot of my network So my json always go as application/json .
ScreenShot235.jpg
I am not configuring my url as application/json rather in json file I am defined content type as text/html. which I can see in second line.

Please let me know what could be solution or do i need to define sepearte store for this ?
The above comes in chrome where as in firefox it askes me to save or open file. dialog box

[skirtle]

I don't understand what it is you think you've done but you need to change the content-type of that response from application/json to text/html. In the screenshot it is clearly wrong. The behaviour you describe in both Chrome and Firefox is exactly what I'd expect given the content-type is wrong.

I don't know how to change the content-type on your server. Please consult with the documentation because whatever you're doing at the moment is incorrect.

[mshepherd]

I had a problem with the file upload too. I noticed that if you put the keys not in quotes it in your response it fixes the issues:

{"success":true} <- does not work
{success:true} <- works, no invalid json error

[Vmani]

Hi ,

I am getting "Uncaught Ext.Error: You're trying to decode an invalid JSON String: " when i try to submit the form with a file upload feature.I tried setting the response to text/html.This doesn't help.
and one more problem is that a fakepath gets add when i upload a file.How to remove this fakepath and display the full path.

I am using struts with extjs.

Please help.
Thanks,
M.Vishwadharini

[george4motion]

So even though I want to parse JSON the response should be set to "text/html" instead of "application/json"? That makes little sense and though it worked for others, it doesn't for me because my JSON can contain an open angle bracket, which is valid in JSON, but which cannot be parsed when the content is text/html. Specifically the following valid JSON property:


"handlingInst":"<DO NOT SEND INVOICES.DO NOT CHARGE FREIGHT>"

Got transformed into the following invalid JSON:


"handlingInst":"<do not=" " send=" " invoices.do=" " charge=" " freight=" ">"

Substituting &lt; seems fraught with problems especially if it can be used in places where it will be displayed that way literally instead of as an angle bracket. We are already overriding JSON.parse so I will probably strip out any surrounding pre tags there, but the main point is that setting the Content-type to text/html can cause problems if the JSON contains angle brackets.

[tonystark]

Judging by that error message it seems that the JSON is coming back wrapped in HTML pre tags. Check the response in Firebug to confirm. If this is the case then your problem is with your server, not ExtJS.