ابحث في الدعم

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

AJAX post request between Cross-sites (CORS) - POST ~7000 Bytes or more data/json on FF36 above Failed

more options

Hello,

We are facing CORS issue with FF36 and above versions while posting 7000 bytes or more data/json object. - When we post approximately 7000 bytes or more JSONObject content through ajax request between Cross-site HTTP request, then the request is failed with 'Aborted' status. I can see an error message on console (Firebug). Same request I will be submitted if the Content-Length is less than 7000 bytes.

Error message: "Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://URL/fulfillment. (Reason: CORS request failed)."

We are not sure what is going wrong with the request. If the issue is with CORS then why it is not happening with FF35 and below version. I can post huge JSON content length while using same service on FF35 or below version. Same we tested in Chrome, it is working perfectly fine with 20000 bytes content length.

Your inputs on this and how to troubleshoot this issue will be very helpful. Is there any specific changes to settings that we need to do in FF36 and above.

Thanks in advance.

Hello, We are facing CORS issue with FF36 and above versions while posting 7000 bytes or more data/json object. - When we post approximately 7000 bytes or more JSONObject content through ajax request between Cross-site HTTP request, then the request is failed with 'Aborted' status. I can see an error message on console (Firebug). Same request I will be submitted if the Content-Length is less than 7000 bytes. Error message: "Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://URL/fulfillment. (Reason: CORS request failed)." We are not sure what is going wrong with the request. If the issue is with CORS then why it is not happening with FF35 and below version. I can post huge JSON content length while using same service on FF35 or below version. Same we tested in Chrome, it is working perfectly fine with 20000 bytes content length. Your inputs on this and how to troubleshoot this issue will be very helpful. Is there any specific changes to settings that we need to do in FF36 and above. Thanks in advance.

Modified by jagadishuppala

All Replies (4)

more options

Hmm, is the post over HTTPS and do you use a CISCO ACE load balancer? Firefox 36 changed something that has an issue in that scenario. See:

more options

Thanks for the quick reply. We will check if this solution works for us or not. I will let you know.

more options

jagadishuppala said

Hello, We are facing CORS issue with FF36 and above versions while posting 7000 bytes or more data/json object. - When we post approximately 7000 bytes or more JSONObject content through ajax request between Cross-site HTTP request, then the request is failed with 'Aborted' status. I can see an error message on console (Firebug). Same request I will be submitted if the Content-Length is less than 7000 bytes. Error message: "Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://URL/fulfillment. (Reason: CORS request failed)." We are not sure what is going wrong with the request. If the issue is with CORS then why it is not happening with FF35 and below version. I can post huge JSON content length while using same service on FF35 or below version. Same we tested in Chrome, it is working perfectly fine with 20000 bytes content length. Your inputs on this and how to troubleshoot this issue will be very helpful. Is there any specific changes to settings that we need to do in FF36 and above. Thanks in advance.

Thanks For the reply! But we have this issue only on Firefox 36 and above versions. IE and Chrome browsers able to post the data properly between cross site services. Even Firefox 35 and below versions are working fine!!!

more options

So in reference to my earlier reply: you either are using HTTP (not HTTPS) or not using that device, or you changed the device configuration and it didn't help?