This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

When uploading large file from network, all other requests are not being sent to server

  • 1 antwoord
  • 1 het hierdie probleem
  • 6 views
  • Laaste antwoord deur guigs

more options

In our application we are facing a weird scenario in which when we try to upload a huge file(600+ MB) from network, all other requests(AJAX) are getting blocked. But when the same file is being uploaded from local location(E drive) then everything works fine.

In our application we are facing a weird scenario in which when we try to upload a huge file(600+ MB) from network, all other requests(AJAX) are getting blocked. But when the same file is being uploaded from local location(E drive) then everything works fine.

Gekose oplossing

How are you uploading the file via network?

If you are troubleshooting the network bandwidth? or the threads where one process takes precedent over the other you will have to troubleshoot the QoS of the network you see this on.

To give a better visual please use Firebug or the Web Developer tool called Network to analyze the requests. The "XMLHttpRequest" will give better clues for Ajax. Reference http://ajaxian.com/archives/ajax-debugging-with-firebug

There may be a about:config option that allows mutithreading or max persistent connections per server you can check.

Lees dié antwoord in konteks 👍 0

All Replies (1)

more options

Gekose oplossing

How are you uploading the file via network?

If you are troubleshooting the network bandwidth? or the threads where one process takes precedent over the other you will have to troubleshoot the QoS of the network you see this on.

To give a better visual please use Firebug or the Web Developer tool called Network to analyze the requests. The "XMLHttpRequest" will give better clues for Ajax. Reference http://ajaxian.com/archives/ajax-debugging-with-firebug

There may be a about:config option that allows mutithreading or max persistent connections per server you can check.