What reasons would rel=preload followed by a fetch of same resource return an incomplete response body?
I am trying to preload a binary asset to get it discovered by the browser earlier and hopefully speed up the rendering of that asset once the application is up and running.
Usually we're fetching that asset with a normal fetch and then reading there that response.
The problem I am facing is, once I add a <link rel="preload" as="fetch" href="my-asset-url" crossorigin="anonymous" /> things start getting weird.
The behavior I am seeing is that the browser is successfully discovering the asset early and preloads it correctly.
Then when the fetch in the app code executes (there is no network request going out - which what I would expect since it already preloaded it), the response for that fetch, however, is incomplete - it's returning a partial of what the response is expected (32,768 bytes - consistently out of 393,372 bytes).
I am unable to reproduce this behavior outside of our app code so far. But thought I'd ask to see if anyone might have seen similar behavior like this. Any idea what could cause this?
javascript web fetch preload
asked Nov 21 '18 at 21:29
mkhatibmkhatib
3,27012033
add a comment |
I am trying to preload a binary asset to get it discovered by the browser earlier and hopefully speed up the rendering of that asset once the application is up and running.
Usually we're fetching that asset with a normal fetch and then reading there that response.
The problem I am facing is, once I add a <link rel="preload" as="fetch" href="my-asset-url" crossorigin="anonymous" /> things start getting weird.
The behavior I am seeing is that the browser is successfully discovering the asset early and preloads it correctly.
Then when the fetch in the app code executes (there is no network request going out - which what I would expect since it already preloaded it), the response for that fetch, however, is incomplete - it's returning a partial of what the response is expected (32,768 bytes - consistently out of 393,372 bytes).
I am unable to reproduce this behavior outside of our app code so far. But thought I'd ask to see if anyone might have seen similar behavior like this. Any idea what could cause this?
javascript web fetch preload
asked Nov 21 '18 at 21:29
mkhatibmkhatib
3,27012033
add a comment |
I am trying to preload a binary asset to get it discovered by the browser earlier and hopefully speed up the rendering of that asset once the application is up and running.
Usually we're fetching that asset with a normal fetch and then reading there that response.
The problem I am facing is, once I add a <link rel="preload" as="fetch" href="my-asset-url" crossorigin="anonymous" /> things start getting weird.
The behavior I am seeing is that the browser is successfully discovering the asset early and preloads it correctly.
Then when the fetch in the app code executes (there is no network request going out - which what I would expect since it already preloaded it), the response for that fetch, however, is incomplete - it's returning a partial of what the response is expected (32,768 bytes - consistently out of 393,372 bytes).
I am unable to reproduce this behavior outside of our app code so far. But thought I'd ask to see if anyone might have seen similar behavior like this. Any idea what could cause this?
javascript web fetch preload
asked Nov 21 '18 at 21:29
mkhatibmkhatib
3,27012033
I am trying to preload a binary asset to get it discovered by the browser earlier and hopefully speed up the rendering of that asset once the application is up and running.
Usually we're fetching that asset with a normal fetch and then reading there that response.
The problem I am facing is, once I add a <link rel="preload" as="fetch" href="my-asset-url" crossorigin="anonymous" /> things start getting weird.
The behavior I am seeing is that the browser is successfully discovering the asset early and preloads it correctly.
Then when the fetch in the app code executes (there is no network request going out - which what I would expect since it already preloaded it), the response for that fetch, however, is incomplete - it's returning a partial of what the response is expected (32,768 bytes - consistently out of 393,372 bytes).
I am unable to reproduce this behavior outside of our app code so far. But thought I'd ask to see if anyone might have seen similar behavior like this. Any idea what could cause this?
javascript web fetch preload
javascript web fetch preload
asked Nov 21 '18 at 21:29
mkhatibmkhatib
3,27012033
asked Nov 21 '18 at 21:29
mkhatibmkhatib
3,27012033
asked Nov 21 '18 at 21:29
mkhatibmkhatib
3,27012033
asked Nov 21 '18 at 21:29
mkhatibmkhatib
3,27012033
asked Nov 21 '18 at 21:29
mkhatibmkhatib
3,27012033
3,27012033
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53420719%2fwhat-reasons-would-rel-preload-followed-by-a-fetch-of-same-resource-return-an-in%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53420719%2fwhat-reasons-would-rel-preload-followed-by-a-fetch-of-same-resource-return-an-in%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
