Feature Request P2
Status Update
Comments
pv...@google.com <pv...@google.com> #2
Hello,
Thank you for reaching out to us!
This issue seems to be outside of the scope of Issue Tracker. This Issue Tracker is a forum for end users to report bugs
and request features
on Google Cloud products. Please go through
I recommend you to
For now, I'm going to close this thread which will no longer be monitored. In case you want to report a new issue, please do not hesitate to create a new Issue Tracker describing your issue.
Thank you!
po...@gmail.com <po...@gmail.com> #3
[Comment deleted]
sa...@gmail.com <sa...@gmail.com> #4
frederikcreemers did you solve the problem ?
I'm facing it right now... :(
I'm facing it right now... :(
bo...@gmail.com <bo...@gmail.com> #5
I am amazed that this is not supported.
jo...@google.com <jo...@google.com> #6
FWIW regarding the initial request: AJAX-crawling is being deprecated, so going forward you wouldn't need to handle ?_escaped_fragment_= requests for URLs with #! or meta-fragment.
https://webmasters.googleblog.com/2015/10/deprecating-our-ajax-crawling-scheme.html
Description
Consider the following app.yaml rule:
- url: /app\?_escaped_fragment=
script:
This won't work, because App Engine only matches the path against the regular expression. I'd like this to work.
#If relevant, what new use cases will this feature will enable?
Let's say your application routes all users to a static file, that does further routing using javascript. This is very useful, because serving static files is cheaper than hitting a script handler. This file communicates with your ap through, for instance, a cloud endpoints API. 'This works great for users, but isn't very crawler friendly.
We can fix this by implementing the crawlable AjAx specification, documented here:
.
Now if my static file is crawled through the path /app, Googlebot will find the meta tag described in the spec, and make a request to /app?_escaped_fragment_=, but there's currently no way for me to route this request to a script handler instead of a static file handler in app.yaml.
A current workaround is to have a script handler route the request based on the presence of the _escaped_fragment_ query parameter, but the goal of having a static file, is requests not hitting the app server at all.