Tapestry 5
  1. Tapestry 5
  2. TAP5-1701

If the incoming request does not include a locale in the path, the application uses the server locale (not a locale extracted from the request headers)

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 5.3
    • Fix Version/s: 5.3
    • Component/s: tapestry-core
    • Labels:
      None

      Description

      Somewhere the code that's supposed to extract the locale from the request and invoke LocalizationSetter.setNonPeristentLocaleFromLocaleName() got lost!

        Activity

          People

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

            Dates

            • Created:
              Updated:
              Resolved:

              Development