HTTP heartbeat to avoid connection drop for long running http calls












1















I have an app deployed on Heroku PaaS.



They have a timeout policy like this (https://devcenter.heroku.com/articles/request-timeout):



30 seconds, extending by 55 seconds each time a byte is sent or received in the connection.



I have http endpoints that can take a while (upload file, take some time to ingest it, and return 200 ok).
If the processing takes more than 30 seconds, to connection is dropped by Heroku router, and the whole thing is aborted.



There are plain HTTP/JSON API endpoints.
Client is Angular 6+, server is Spring Boot 2+ (Spring MVC, no reactive stuff).



I know I could make the process asynchronous, no need to point me in that direction.



The question is: is there a way to keep sending stuff in the connection while the data are being processed, either from the browser or from the server side ?



Some kind of keepalive noise, like what can be done in a SSH connection.



Something I could add in the Angular app as an interceptor would be perfect.










share|improve this question



























    1















    I have an app deployed on Heroku PaaS.



    They have a timeout policy like this (https://devcenter.heroku.com/articles/request-timeout):



    30 seconds, extending by 55 seconds each time a byte is sent or received in the connection.



    I have http endpoints that can take a while (upload file, take some time to ingest it, and return 200 ok).
    If the processing takes more than 30 seconds, to connection is dropped by Heroku router, and the whole thing is aborted.



    There are plain HTTP/JSON API endpoints.
    Client is Angular 6+, server is Spring Boot 2+ (Spring MVC, no reactive stuff).



    I know I could make the process asynchronous, no need to point me in that direction.



    The question is: is there a way to keep sending stuff in the connection while the data are being processed, either from the browser or from the server side ?



    Some kind of keepalive noise, like what can be done in a SSH connection.



    Something I could add in the Angular app as an interceptor would be perfect.










    share|improve this question

























      1












      1








      1








      I have an app deployed on Heroku PaaS.



      They have a timeout policy like this (https://devcenter.heroku.com/articles/request-timeout):



      30 seconds, extending by 55 seconds each time a byte is sent or received in the connection.



      I have http endpoints that can take a while (upload file, take some time to ingest it, and return 200 ok).
      If the processing takes more than 30 seconds, to connection is dropped by Heroku router, and the whole thing is aborted.



      There are plain HTTP/JSON API endpoints.
      Client is Angular 6+, server is Spring Boot 2+ (Spring MVC, no reactive stuff).



      I know I could make the process asynchronous, no need to point me in that direction.



      The question is: is there a way to keep sending stuff in the connection while the data are being processed, either from the browser or from the server side ?



      Some kind of keepalive noise, like what can be done in a SSH connection.



      Something I could add in the Angular app as an interceptor would be perfect.










      share|improve this question














      I have an app deployed on Heroku PaaS.



      They have a timeout policy like this (https://devcenter.heroku.com/articles/request-timeout):



      30 seconds, extending by 55 seconds each time a byte is sent or received in the connection.



      I have http endpoints that can take a while (upload file, take some time to ingest it, and return 200 ok).
      If the processing takes more than 30 seconds, to connection is dropped by Heroku router, and the whole thing is aborted.



      There are plain HTTP/JSON API endpoints.
      Client is Angular 6+, server is Spring Boot 2+ (Spring MVC, no reactive stuff).



      I know I could make the process asynchronous, no need to point me in that direction.



      The question is: is there a way to keep sending stuff in the connection while the data are being processed, either from the browser or from the server side ?



      Some kind of keepalive noise, like what can be done in a SSH connection.



      Something I could add in the Angular app as an interceptor would be perfect.







      angular http spring-boot heroku timeout






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 22 '18 at 7:05









      rcomblenrcomblen

      3,6161927




      3,6161927
























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


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53425517%2fhttp-heartbeat-to-avoid-connection-drop-for-long-running-http-calls%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
















          draft saved

          draft discarded




















































          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53425517%2fhttp-heartbeat-to-avoid-connection-drop-for-long-running-http-calls%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

          If I really need a card on my start hand, how many mulligans make sense? [duplicate]

          Alcedinidae

          Can an atomic nucleus contain both particles and antiparticles? [duplicate]