Open Bug 1798442 Opened 2 years ago Updated 1 year ago

upload of file should continue after wifi reconnection

Categories

(Core :: DOM: Networking, defect, P2)

Firefox 106
defect

Tracking

()

UNCONFIRMED

People

(Reporter: radica_dude, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:106.0) Gecko/20100101 Firefox/106.0

Steps to reproduce:

Upload large file to aws
while uploading wifi got disconnected
wifi gets reconnected

Actual results:

upload did not continue

Expected results:

upload api call should continue uploading the file

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:106.0) Gecko/20100101 Firefox/106.0

Hi,

Thank you for opening this enhancement. I will set this as New and waiting for the developer's opinion about it.

Thanks for your input.

Status: UNCONFIRMED → NEW
Component: Untriaged → Networking
Ever confirmed: true
Product: Firefox → Core

Do other web browsers do this for the site in question?
This seems like something that might be the web developer's responsibility.

Flags: needinfo?(radica_dude)

Agreed. This isn't something browsers can do automatically at this point. We might get there in the future.
@radica_dude, kindly please test to see what happens with other browsers.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED

Right now chrome browser resumes the upload.

I can handle this scenario if firefox closes the fetch call and throws an error.
Also added timeout for now and abort the fetch after timeout is reached.

Right now what is happening is the fetch call is still active and doing nothing.

It would be nice if the upload can continue or just abort the fetch call.

Flags: needinfo?(radica_dude)

Would you be able to capture some logs?
https://firefox-source-docs.mozilla.org/networking/http/logging.html

Or otherwise send us a HAR output of the fetch call in devtools?
If the fetch just hangs, then that sounds like a bug.

Status: RESOLVED → REOPENED
Flags: needinfo?(radica_dude)
Resolution: INVALID → ---

Here is the put request

{
"pageref": "page_1",
"startedDateTime": "2022-11-04T15:16:35.465+04:00",
"request": {
"bodySize": 0,
"method": "PUT",
"url": "https://........amazonaws.com",
"httpVersion": "",
"headers": [
{
"name": "Host",
"value": ".....amazonaws.com"
},
{
"name": "User-Agent",
"value": "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:106.0) Gecko/20100101 Firefox/106.0"
},
{
"name": "Accept",
"value": "/"
},
{
"name": "Accept-Language",
"value": "en-US,en;q=0.5"
},
{
"name": "Accept-Encoding",
"value": "gzip, deflate, br"
},
{
"name": "Referer",
"value": "http://local:3000/"
},
{
"name": "Content-Length",
"value": "209715200"
},
{
"name": "Origin",
"value": "http://local:3000"
},
{
"name": "DNT",
"value": "1"
},
{
"name": "Connection",
"value": "keep-alive"
},
{
"name": "Sec-Fetch-Dest",
"value": "empty"
},
{
"name": "Sec-Fetch-Mode",
"value": "cors"
},
{
"name": "Sec-Fetch-Site",
"value": "cross-site"
},
{
"name": "Pragma",
"value": "no-cache"
},
{
"name": "Cache-Control",
"value": "no-cache"
}
],
"cookies": [],
"queryString": [
{
"name": "X-Amz-Algorithm",
"value": "AWS4-HMAC-SHA256"
},
{
"name": "X-Amz-Content-Sha256",
"value": "UNSIGNED-PAYLOAD"
},
{
"name": "X-Amz-Credential",
"value": "...."
},
{
"name": "X-Amz-Date",
"value": "20221104T111633Z"
},
{
"name": "X-Amz-Expires",
"value": "3600"
},
{
"name": "X-Amz-Signature",
"value": "...."
},
{
"name": "X-Amz-SignedHeaders",
"value": "host"
},
{
"name": "partNumber",
"value": "1"
},
{
"name": "uploadId",
"value": "...."
},
{
"name": "x-id",
"value": "UploadPart"
}
],
"headersSize": 1135
},
"response": {
"status": 0,
"statusText": "",
"httpVersion": "",
"headers": [],
"cookies": [],
"content": {},
"redirectURL": "",
"bodySize": -1
},
"cache": {},
"timings": {},
"time": 0
}

Flags: needinfo?(radica_dude)

Hi Reporter,

Is it possible to provide a public link for us to test this?

Thanks.

Flags: needinfo?(radica_dude)

Hi,

Sorry I cannot give you public link to test.
I will try to reproduce it by uploading to google drive and will update this issue.

Thank you for your consideration.

Flags: needinfo?(radica_dude)
Blocks: fetch
Severity: -- → S3
Type: enhancement → defect
Component: Networking → DOM: Networking
Priority: -- → P2
Whiteboard: [necko-triaged]
Status: REOPENED → UNCONFIRMED
Ever confirmed: false
You need to log in before you can comment on or make changes to this bug.