Question

I have a JSON format result sent back to the client that hold the $quot sign. for some unknown reason the code breaks.

Here is the code that bricks from ext-all-debug:

doDecode = function(json){
   return eval("(" + json + ")");    FAILS HERE
},

Here is my JSON as it left the server (As far as I know , I hope the server doesn’t take the time to decode this &quot on its free time.):

{
success: true,
total: 1,
results: [{
    "ID": -1,
    "Value": "POChangeRequestlblCustomerCatalogNumber",
    "Description": "",
    "Labels": {
        "1": {
            "ID": -1,
            "LanguageID": 1,
            "Value": "Catalog Number",
            "ToolTip": "",
            "LanguageName": "English",
            "KeyID": -1,
            "KeyValue": "POChangeRequestlblCustomerCatalogNumber",
            "KeyDescription": ""
        },
        "2": {
            "ID": -1,
            "LanguageID": 2,
            "Value": "&quot;", <<< THIS IS THE BAD PART!!!
            "ToolTip": "",
            "LanguageName": "Hebrew",
            "KeyID": -1,
            "KeyValue": "POChangeRequestlblCustomerCatalogNumber",
            "KeyDescription": ""
        }
    },
    "ServerComments": "1"
}]
}

this JSON is sent in a text/html content type as it is the result of a file upload operation. could that be part of the problem?

Ok, I have continued to trace down the problem and found that ExtJS does this function on the returned value from a hidden iframe:

doFormUpload : function(o, ps, url){
        ...

            try{
                doc = frame.contentWindow.document || frame.contentDocument || WINDOW.frames[id].document;
                if(doc){
                    if(doc.body){
                        if(/textarea/i.test((firstChild = doc.body.firstChild || {}).tagName)){ 
                            r.responseText = firstChild.value;
                        }else{
                            r.responseText = doc.body.innerHTML;  << THIS IS WHERE MY &quot; get decoded back to " (sign)
                        }
                    }

                    r.responseXML = doc.XMLDocument || doc;
                }
            }
            catch(e) {}

            ...
    }

Is there a good workaround for this issue. it seems that the browser automatically decodes the value???? any one???? this is a major issue !!

Answer 1

Here is how I worked around it.

The problem was that all browsers automatically decode the & quot; signs.

So I have fixed the Ext doFormUpload function to look like this:

  doFormUpload : function(o, ps, url){
    ...

        try{
            doc = frame.contentWindow.document || frame.contentDocument || WINDOW.frames[id].document;
            if(doc){
                if(doc.body){
                    if(doc.body.innerText){
                            r.responseText = doc.body.innerText;
                        }else{
                            r.responseText = doc.body.innerHTML.replace(/<pre>/ig,'').replace(/<\/pre>/ig,'');
                        }
                }

                r.responseXML = doc.XMLDocument || doc;
            }
        }
        catch(e) {}

        ...
}

In addition from now on the content type that the server is returning is “text/plain”
this prevents the browsers from decoding the data.
I also added a little workaround from FF that does not support innerText property but adds the tag that wraps the response.

This is an ugly hack to the ExJS framwork but it worked for me.

Hopefully someone will notice the question and have some better idea on how to solve it.