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!
javascript angularjs node.js angular
asked Nov 8 at 11:49
user3527354
334214
add a comment |
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!
javascript angularjs node.js angular
asked Nov 8 at 11:49
user3527354
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
add a comment |
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!
javascript angularjs node.js angular
asked Nov 8 at 11:49
user3527354
334214
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
javascript angularjs node.js angular
asked Nov 8 at 11:49
user3527354
334214
asked Nov 8 at 11:49
user3527354
334214
asked Nov 8 at 11:49
user3527354
334214
asked Nov 8 at 11:49
user3527354
334214
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
add a comment |
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
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f53207153%2fhow-to-i-force-the-front-end-to-not-time-out%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
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