Open Bug 1916750 Opened 1 year ago Updated 1 year ago

Firefox sometimes doesn't display response data for network requests

Categories

(DevTools :: Netmonitor, defect, P3)

defect

Tracking

(Not tracked)

People

(Reporter: jrmuizel, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

When trying to debug 1913938 I sometimes get no request/response data in the network inspector when getting:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://cdn.grupoelcorteingles.es/statics/front-msh2-lloyds/assets/firefly/javascripts/assets/Layout-7cf64fce.js. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200.

Sometimes I will get a CORS header ‘Access-Control-Allow-Origin’ missing) error showing up in the network inspector.

See Also: → 1913938

I can repro this at times. Shift-reload helps. Generally once it happens, it keeps happening on Reload. Shift-reload can cause it to fix itself, but it may fail to do that for long periods. Clearing site data caused it to fix itself; until shit-reloads eventually caused to fail again.

Anytime it fails, there are numerous CORS failures like:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://cdn.grupoelcorteingles.es/statics/front-msh2-lloyds/assets/firefly/javascripts/assets/ContextMenu-12b5d723.js. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 200

Any time it fails, it also doesn't show Descárgate aquí nuestra App. in a banner - this is likely due to the CORS failures.

I have seen it fix itself with plain Reload once.

Flags: needinfo?(jdescottes)

This might also get fixed by the work on incomplete requests handling.

Severity: -- → S3
Flags: needinfo?(jdescottes)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: