Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

לאתר זה תהיה פונקציונליות מוגבלת בזמן שאנו מתחזקים אותו לשיפור החוויה שלך. אם מאמר מסויים לא פותר את הבעיה שלך וברצונך לשאול שאלה, קהילת התמיכה שלנו מחכה לעזור לך ב־Twitter תחת ‎@FirefoxSupport וב־Reddit תחת ‎/r/firefox.

חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

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

  • 1 תגובה
  • 1 has this problem
  • 6 views
  • תגובה אחרונה מאת 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.

פתרון נבחר

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.

Read this answer in context 👍 0

כל התגובות (1)

more options

פתרון נבחר

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.