Tapestry 5
  1. Tapestry 5
  2. TAP5-422

Tapestry should encode the user's locale into the URL rather than as an HTTP cookie

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.1.0.0
    • Fix Version/s: 5.1.0.0
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      It would be nice if the user's locale showed up in the URL, perhaps just after the context path. Example:

      /context/en/article or /context/de/admin/edit.

      This would make the link encoding and decoding rules more complex, as it should still support the current URLs. Basically, it will have to see if the first "folder" in the request path matches one of the configured locales.

        Activity

        Hide
        Howard M. Lewis Ship added a comment -

        This occured to me because a web spider, such as Google, will only be able to see one localization of an application (typically the default, or English, version).

        Show
        Howard M. Lewis Ship added a comment - This occured to me because a web spider, such as Google, will only be able to see one localization of an application (typically the default, or English, version).

          People

          • Assignee:
            Howard M. Lewis Ship
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development