Develop Reference

Limit on number of cookies allowed? - err_spdy_protocol_error

On Chrome and Firefox I sometimes get the following error err_spdy_protocol_error
once I call the following website https://checkideas.com/.
I have researched on this topic on the internet and on this platform as well. I also found a working solution. Once I delete all the cookies and reload the webpage the error does not emerge.
So if you click on the website for the 1st time it will definitely work. But once there are number of cookies given the website cannot always be called. This is only the pattern I have identified so far. However I would like to have a sustainable solution.
What do I have to do to avoid this issue so that this issue does not occur? What is the source of the error?
Unfortunately following responses on similar questions did not answer my question:
Console errors. Failed to load resource: net::ERR_INSECURE_RESPONSE
What mean ERR_SPDY_PROTOCOL_ERROR in nginx?
I also cannot identify any issue with the certificate.

This error is related to the SPDY Protocol or an antivirus setting.
Updating to a later version of the browser should help fix the error (Google Chrome and Mozilla have dropped support for the SPDY Protocol.
This article contains methods that should help you fix the ERR_SPDY_PROTOCOL_ERROR
on Google Chrome or Mozilla.

XHR Post aborted in Firefox > 44, Safari and IE, but always Works in Chrome

I have a piece of Javascript fully tested and working in many different environments. In this new environment I'm currently facing, this script does not work even using the same browsers.
The problem is the following: this script does and XHR Post to a certain URL (in the same domain) but in Firefox 46 (it DOES work in firefox 43 and 44) and Safari I see in the network monitor "Aborted". In IE randomly works, otherwise remains in pending. It always works in Chrome.
Trying to debug the problem I used Fiddler, but Fiddler seems to solve the problem with all the browsers.
The website is in HTTPS, but I don't think it's an HTTPS related problem because I can directly access to the resource and I can successfully do the same POST with CURL.
It also seems to be a Client Side problem because with Whireshark I can't even see the begin of the request. It seems like the browser drops the XHR POST even before starting it.
What can be the root of this problem? What changed between firefox 44 and 46 regarding the handling of HTTP POST request?
Thanks in advance.
PS: unfortunately I cannot share the code. Anyway, since it does works in different infrastractures, maybe is not needed.
UPDATE1: I just noticed that if I wait a couple of seconds (around 30) and I do "Edit and resend" from the network monitor, the request is correctly sent. If i try before that windowd time I see the "aborted" error

This seems to be a bug in Firefox 46: http://forums.mozillazine.org/viewtopic.php?f=25&t=3005573
I just upgraded to Firefox 47, and it appears to be solved now.

thank you for your answer. You were right about Firefox, in fact I upgraded to 47 too and it was solved. Anyway the problem was still present for IE and Safari. I found as a solution, valid for all browsers, enabling the One Connect feature on the Big-IP F5 load balancer. Unfortunately it wasn't something managed by me and I hadn't access to this kind of configuration to do some tests by myself
I hope this information can be useful to someone else encountering the same problem

Enyo ajax request fails in mobile Safari 7, works elsewhere

I have a web app that makes cross-domain Ajax requests. The requests go through without a problem in almost every environment except for iOS devices (iPad, iPhone) running Safari 7. On those devices, the request fails. It works with the latest desktop Safari and also with mobile Safari 5; the problem is only with mobile Safari 7 (and perhaps 6; I don't have access to one of those for testing).
The app first makes a GET request to the origin site (with http protocol), which works fine. It then makes an https POST request to a different site (which is correctly configured for CORS). This is the request that fails. Nothing appears in the Safari console when the request fails and the server logs indicate that no request arrived.
One more detail that may or may not be relevant: the sequence of two requests is triggered by a single user action.
Does anyone have an idea of what's going on here?
EDIT The problem definitely appears to be related to Enyo. I created this fiddle that demonstrates the problem. If you are using Mobile Safari 7 and select enyo.Ajax as the tool for making the request, it will fail. The same request to the same URL will succeed using an XMLHttpRequest object directly. (The server-side script simply echoes the request headers. It also adds
Access-Control-Allow-Origin: *
to the response.)

Looks like this was related to a fix we made for iOS to prevent caching of non-cacheable requests. This fix was updated to only apply to iOS 6 in 2.3.0: https://github.com/enyojs/enyo/commit/73ade2a9dd68deb2f4a4db548c45e2c27104632f
Per the comments in the fix, you can use the header property to specify an object with cache-control: null, unless you're planning on upgrading to 2.3.0. :)

I ran this by the Enyo framework team. No one is exactly sure why you might be having the problem but it could be:
1) This: iOS 7 javascript XMLHttpRequest bug
2) A certificate issue with the https server.
It doesn't appear to be a framework issue, though. If the answer is something else, please let us know!

IE11 does not send HTTP POST data

I have a problem with sending data using XMLHttpRequest and/or ActiveXObject("Microsoft.XMLHTTP").
I can't even get the example from w3schools to work :( - http://www.w3schools.com/ajax/tryit.asp?filename=tryajax_post2
The problem is that there is the request to server, but it totally ignores the argument from the following code and no data arrives to server.
xmlhttp.send("fname=Henry&lname=Ford")
Is it a bug of IE11, or should it be done in another way?
I've tried using both ActiveXObject and XMLHttpRequest.

Yes, it works in my IE 11.
Did you test your code in chrome, and debug it where it causes error?

I have the same problem with IE11/Windows7, it doesn't happen all the time. It is certainly a bug in IE11. all other browser work just fine. As a workaround, I have to use "GET". You can do the same.
I recommend that you ask someone from Microsoft browser team to take a look at this.

File upload sometimes not working on IE9

I am using valums ajax-upload together with a ashx handler to let users upload files in the webapp Im developing. All is working absolutely fine for about 95% (around 3000) of the users.
For the last about 5% I get reports that the upload never finish, the wheel just keeps spinning people say. It seems that those who get this error are all are using IE9.0.
I have tested on all the IE9.0 I can come across but still have not been able to reproduce the error. I also have tried to log all thinkable errors but still no luck.
Please, can anyone reproduce the problem and hopefully give me a JavaScript console error transcript if any. To test go to step 2 (Upload section) and try to upload a small text file:
https://jobmatchprofile.com/backend/login.aspx?auto_login=24G3FY
UPDATE
I have been in contact with a user who experienced this problem. The error message can be seen here. It is in danish and says: "SCRIPT5 Access denied".
Error message
What is strange is that the user had same IE version as is working for others (me for example): I have been testing on: 9.0.8112.16421 and also ran WIN7 (as I). The Product-id differs however and he had a danish version where I have the US version.
UPDATE II
I was finally able to reproduce this error. I know this sounds a little strange, but belive me it is true: when opening the page via a link sent to my gmail account I get the same error. The user from first Update also used gmail to open the page.

Your reference to Gmail, specifically, points in the direction of a solution: Gmail strips the referrer data from the HTTP headers when you click on a link within an e-mail, except when you use your right mouse button and select "Open in New Tab [or Window]", presumably because this prevents their code from intercepting the headers. Is your script checking for a valid HTTP REFERRER, by any chance?
Are you making any cross-(sub)domain or cross-protocol AJAX calls? If so, then you may have to proxy the request(s). Consider the following solutions from the Yahoo! Developer Network:
http://developer.yahoo.com/javascript/howto-proxy.html
See also:
SCRIPT5: Access is denied in IE9 on xmlhttprequest
Access denied to jQuery script on IE
"Access is denied" JavaScript error when trying to access the document object of a programmatically-created <iframe> (IE-only)
(Un)fortunately, I wasn't able to reproduce the error in IE9, v. 9.0.8112.16421 (although I did get a general on-site error when trying to upload an empty .txt file, but this seems wholly unrelated).

The solution for ie9 is simply to upload using https:
https://www.parse.com/questions/internet-explorer-and-the-javascript-sdk

Even though you are sure that it's related to the user clicking the anchor within the email I would say it's because of policy settings within Internet Explorer. I have seen errors like these before and noticed that the most common errors were related to Internet Explorer policies of users within a corporate environment.