How to I force the front end to not time out?











up vote
-1
down vote

favorite












I am waiting for a response from the server which is generating a rather large file. The file takes a long time to produce, so I usually get a time out error on the front end.



How do I make it not time out and wait for the response?



Frontend is in angular. Backend is in Node.



Thanks in advance!










share|improve this question






















  • which angular? what version? You should also post some of your code
    – Aleksey Solovey
    Nov 8 at 11:50






  • 1




    This seems something which you needs to handle it in service side to increase timeout but nothing to do with client side.
    – Immanuel Kirubaharan
    Nov 8 at 12:06










  • Instead of waiting for the file to be built on the backend, why not use streams to pipe the data back to the client as the backend processes it? That way, the client is receiving regular chunks of data, which means you don't get the timeout.
    – Chris Adams
    Nov 8 at 12:31










  • You can modify the timeout settings only in Firefox and IE (not on Chrome, unfortunately). So, even with setting an infinite (kinda) timeout on Node, you would end up with the same problem
    – Dyd666
    Nov 8 at 20:41















up vote
-1
down vote

favorite












I am waiting for a response from the server which is generating a rather large file. The file takes a long time to produce, so I usually get a time out error on the front end.



How do I make it not time out and wait for the response?



Frontend is in angular. Backend is in Node.



Thanks in advance!










share|improve this question






















  • which angular? what version? You should also post some of your code
    – Aleksey Solovey
    Nov 8 at 11:50






  • 1




    This seems something which you needs to handle it in service side to increase timeout but nothing to do with client side.
    – Immanuel Kirubaharan
    Nov 8 at 12:06










  • Instead of waiting for the file to be built on the backend, why not use streams to pipe the data back to the client as the backend processes it? That way, the client is receiving regular chunks of data, which means you don't get the timeout.
    – Chris Adams
    Nov 8 at 12:31










  • You can modify the timeout settings only in Firefox and IE (not on Chrome, unfortunately). So, even with setting an infinite (kinda) timeout on Node, you would end up with the same problem
    – Dyd666
    Nov 8 at 20:41













up vote
-1
down vote

favorite









up vote
-1
down vote

favorite











I am waiting for a response from the server which is generating a rather large file. The file takes a long time to produce, so I usually get a time out error on the front end.



How do I make it not time out and wait for the response?



Frontend is in angular. Backend is in Node.



Thanks in advance!










share|improve this question













I am waiting for a response from the server which is generating a rather large file. The file takes a long time to produce, so I usually get a time out error on the front end.



How do I make it not time out and wait for the response?



Frontend is in angular. Backend is in Node.



Thanks in advance!







javascript angularjs node.js angular






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 8 at 11:49









user3527354

334214




334214












  • which angular? what version? You should also post some of your code
    – Aleksey Solovey
    Nov 8 at 11:50






  • 1




    This seems something which you needs to handle it in service side to increase timeout but nothing to do with client side.
    – Immanuel Kirubaharan
    Nov 8 at 12:06










  • Instead of waiting for the file to be built on the backend, why not use streams to pipe the data back to the client as the backend processes it? That way, the client is receiving regular chunks of data, which means you don't get the timeout.
    – Chris Adams
    Nov 8 at 12:31










  • You can modify the timeout settings only in Firefox and IE (not on Chrome, unfortunately). So, even with setting an infinite (kinda) timeout on Node, you would end up with the same problem
    – Dyd666
    Nov 8 at 20:41


















  • which angular? what version? You should also post some of your code
    – Aleksey Solovey
    Nov 8 at 11:50






  • 1




    This seems something which you needs to handle it in service side to increase timeout but nothing to do with client side.
    – Immanuel Kirubaharan
    Nov 8 at 12:06










  • Instead of waiting for the file to be built on the backend, why not use streams to pipe the data back to the client as the backend processes it? That way, the client is receiving regular chunks of data, which means you don't get the timeout.
    – Chris Adams
    Nov 8 at 12:31










  • You can modify the timeout settings only in Firefox and IE (not on Chrome, unfortunately). So, even with setting an infinite (kinda) timeout on Node, you would end up with the same problem
    – Dyd666
    Nov 8 at 20:41
















which angular? what version? You should also post some of your code
– Aleksey Solovey
Nov 8 at 11:50




which angular? what version? You should also post some of your code
– Aleksey Solovey
Nov 8 at 11:50




1




1




This seems something which you needs to handle it in service side to increase timeout but nothing to do with client side.
– Immanuel Kirubaharan
Nov 8 at 12:06




This seems something which you needs to handle it in service side to increase timeout but nothing to do with client side.
– Immanuel Kirubaharan
Nov 8 at 12:06












Instead of waiting for the file to be built on the backend, why not use streams to pipe the data back to the client as the backend processes it? That way, the client is receiving regular chunks of data, which means you don't get the timeout.
– Chris Adams
Nov 8 at 12:31




Instead of waiting for the file to be built on the backend, why not use streams to pipe the data back to the client as the backend processes it? That way, the client is receiving regular chunks of data, which means you don't get the timeout.
– Chris Adams
Nov 8 at 12:31












You can modify the timeout settings only in Firefox and IE (not on Chrome, unfortunately). So, even with setting an infinite (kinda) timeout on Node, you would end up with the same problem
– Dyd666
Nov 8 at 20:41




You can modify the timeout settings only in Firefox and IE (not on Chrome, unfortunately). So, even with setting an infinite (kinda) timeout on Node, you would end up with the same problem
– Dyd666
Nov 8 at 20:41

















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',
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
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53207153%2fhow-to-i-force-the-front-end-to-not-time-out%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53207153%2fhow-to-i-force-the-front-end-to-not-time-out%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Guess what letter conforming each word

Port of Spain

Run scheduled task as local user group (not BUILTIN)