Skip to content

fix: Implement networkOnly.handle using cloned context with Edge #22975

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
TatuLund wants to merge 3 commits into from
Closed

fix: Implement networkOnly.handle using cloned context with Edge #22975

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
62b2e1d
Implement fetch timeout for network requests
TatuLund Dec 12, 2025
c4966bc
Improve fetch handling for Edge browser
TatuLund Dec 12, 2025
b1335eb
Merge branch 'main' into fix-22954
TatuLund Dec 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion flow-server/src/main/resources/com/vaadin/flow/server/frontend/sw.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,7 +134,10 @@ registerRoute(
// Sometimes navigator.onLine is not reliable,
// try to serve the resource from the cache also in the case of a network failure.
try {
return await networkOnly.handle(context);
const { request } = context;
const isEdge = /Edg/.test(self.navigator.userAgent);
const newContext = { ...context, request: request.clone() };
return await networkOnly.handle(isEdge ? newContext : context);
} catch (error) {
const response = await serveResourceFromCache();
if (response) {
Expand Down
Loading