Re: #'s before final /'s in URLs

[Naohiro Aota <naota@xxxxxxxxx>]

On Fri, Nov 23, 2012 at 11:39 AM,  <jidanni@xxxxxxxxxxx> wrote:
>>>>>> "na" == nao aota <nao.aota@xxxxxxxxx> writes:
> na> No. This is fine. Please see http://tools.ietf.org/html/rfc3986
>
> OK, but then what should be done about the fact that
> https://productforums.google.com/d/msg/business/-TtCFKQwiAk/QP1G63382-YJ
> does not get stuck in all browsers except emacs-w3m?

What do you mean with "not get stuck" and ""all browsers"?

If the answer is "it shows the contents" and "Firefox, even without
JavaScript". The following is what is happening on Firefox.

1. The page is using ajax (JavaScript) to retreive the contents.
Strings after "#" is used by JavaScript as a index to the contents.
2. However with using ajax, crawler cannot read the contents and
create search index of the page.
3. So Google suggest to use a hash fragment begging with "#!". The
their crawler replace "#!" with "&_escaped_fragment_=" so that it can
read light weight contents to index it.
https://developers.google.com/webmasters/ajax-crawling/docs/specification
4. Firefox might be understanding this trick. It might be redirecting
to this "_escaped_fragment_" URL when you cannot use JavaScript.

OK. emacs-w3m also can implement this. But this might be something
need time to implement.

Naohiro
Regards