App Engine go111 Beta routing/handler wildcard ignores order?











up vote
1
down vote

favorite












I just tried the GO 1.11 App Engine Beta and the router/handler seems to be different. I use RESTful-VueJS approach and I used the following handler config:



- url: /v1/.*
script: auto
redirect_http_response_code: 301
secure: always

- url: /worker/.*
script: auto
redirect_http_response_code: 301
login: admin

- url: /.*
mime_type: text/html
static_files: static/public/index.html
upload: static/public/index.html
redirect_http_response_code: 301
secure: always


In the first app engine generation the order of the handlers matters, the 1st one with a matching pattern wins. But this doesn't seem to work like this anymore. So even when I call a "/v1/xyz" I always receive the "index.html"



I guess that has to do with the fact that now in app engine all traffic is served using the entrypoint command. As far as I understand it tries to match HandleFuncs() that are set in main() or init()? And what if you use any web framework like me were you don't specify the routes in main() or init() because you want to use mux?










share|improve this question




























    up vote
    1
    down vote

    favorite












    I just tried the GO 1.11 App Engine Beta and the router/handler seems to be different. I use RESTful-VueJS approach and I used the following handler config:



    - url: /v1/.*
    script: auto
    redirect_http_response_code: 301
    secure: always

    - url: /worker/.*
    script: auto
    redirect_http_response_code: 301
    login: admin

    - url: /.*
    mime_type: text/html
    static_files: static/public/index.html
    upload: static/public/index.html
    redirect_http_response_code: 301
    secure: always


    In the first app engine generation the order of the handlers matters, the 1st one with a matching pattern wins. But this doesn't seem to work like this anymore. So even when I call a "/v1/xyz" I always receive the "index.html"



    I guess that has to do with the fact that now in app engine all traffic is served using the entrypoint command. As far as I understand it tries to match HandleFuncs() that are set in main() or init()? And what if you use any web framework like me were you don't specify the routes in main() or init() because you want to use mux?










    share|improve this question


























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I just tried the GO 1.11 App Engine Beta and the router/handler seems to be different. I use RESTful-VueJS approach and I used the following handler config:



      - url: /v1/.*
      script: auto
      redirect_http_response_code: 301
      secure: always

      - url: /worker/.*
      script: auto
      redirect_http_response_code: 301
      login: admin

      - url: /.*
      mime_type: text/html
      static_files: static/public/index.html
      upload: static/public/index.html
      redirect_http_response_code: 301
      secure: always


      In the first app engine generation the order of the handlers matters, the 1st one with a matching pattern wins. But this doesn't seem to work like this anymore. So even when I call a "/v1/xyz" I always receive the "index.html"



      I guess that has to do with the fact that now in app engine all traffic is served using the entrypoint command. As far as I understand it tries to match HandleFuncs() that are set in main() or init()? And what if you use any web framework like me were you don't specify the routes in main() or init() because you want to use mux?










      share|improve this question















      I just tried the GO 1.11 App Engine Beta and the router/handler seems to be different. I use RESTful-VueJS approach and I used the following handler config:



      - url: /v1/.*
      script: auto
      redirect_http_response_code: 301
      secure: always

      - url: /worker/.*
      script: auto
      redirect_http_response_code: 301
      login: admin

      - url: /.*
      mime_type: text/html
      static_files: static/public/index.html
      upload: static/public/index.html
      redirect_http_response_code: 301
      secure: always


      In the first app engine generation the order of the handlers matters, the 1st one with a matching pattern wins. But this doesn't seem to work like this anymore. So even when I call a "/v1/xyz" I always receive the "index.html"



      I guess that has to do with the fact that now in app engine all traffic is served using the entrypoint command. As far as I understand it tries to match HandleFuncs() that are set in main() or init()? And what if you use any web framework like me were you don't specify the routes in main() or init() because you want to use mux?







      google-app-engine google-app-engine-go






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 9 at 14:54

























      asked Nov 9 at 13:11









      Tiega

      192215




      192215





























          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%2f53226353%2fapp-engine-go111-beta-routing-handler-wildcard-ignores-order%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




















































          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.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • 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%2f53226353%2fapp-engine-go111-beta-routing-handler-wildcard-ignores-order%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







          這個網誌中的熱門文章

          Xamarin.form Move up view when keyboard appear

          Post-Redirect-Get with Spring WebFlux and Thymeleaf

          Anylogic : not able to use stopDelay()