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?
google-app-engine google-app-engine-go asked Nov 9 at 13:11
Tiega
192215
add a comment |
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?
google-app-engine google-app-engine-go asked Nov 9 at 13:11
Tiega
192215
add a comment |
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?
google-app-engine google-app-engine-go asked Nov 9 at 13:11
Tiega
192215
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 google-app-engine google-app-engine-go asked Nov 9 at 13:11
Tiega
192215
asked Nov 9 at 13:11
Tiega
192215
edited Nov 9 at 14:54
asked Nov 9 at 13:11
Tiega
192215
asked Nov 9 at 13:11
Tiega
192215
asked Nov 9 at 13:11
Tiega
192215
192215
add a comment |
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%2f53226353%2fapp-engine-go111-beta-routing-handler-wildcard-ignores-order%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
