Twice 302 Redirect, Unable to access the app's default language

[szwss]

Hello, thank you very much for providing this package; it has been very helpful to me.

I am currently using Laravel 8 and have installed "mcamara/laravel-localization": "^2.0.1".

Problem Description:

app.locale is set to ja.

Package Configuration:

supportedLocales includes en, ja, and zh-CN.
'useAcceptLanguageHeader' => true,
'hideDefaultLocaleInURL' => true.

Browser:

accept-language: zh-CN,zh;q=0.9

Accessing:

When I access /ja, since ja is the default language, it automatically redirects to / with a 302 status.

This means the system detects that there is no language parameter, then immediately triggers another 302 redirect to the browser's preferred language based on the header.

Question:

Is there an issue with this process? When I want to access the app's default language, due to the browser's header settings, I am unable to access the app's default language at all.

Idea:

Could we check if the request is coming from a 302 redirect? If so, we should not perform another redirect to prevent the situation mentioned above. Alternatively, we could add a configuration option (true or false) that allows developers to decide whether to enable this feature or not.

I am not sure if my concern is valid or if my proposed solution is feasible. Thank you again for providing this package!

[niels-numbers]

Do you have the LocaleSessionRedirect middleware enabled? It only detects the browser's language if the session locale is not set. So in your scenario, there should only be a single redirect.

When you access /ja, the session key locale will be set to ja. Also, the order of your middleware matters—ensure LocaleSessionRedirect comes before LaravelLocalizationRedirectFilter.

[szwss]

Thank you for your reply.

Here's my Kernel.php configuration:

protected $routeMiddleware = [
...
        'localize' => \Mcamara\LaravelLocalization\Middleware\LaravelLocalizationRoutes::class,  
        'localizationRedirect' => \Mcamara\LaravelLocalization\Middleware\LaravelLocalizationRedirectFilter::class,  
        'localeSessionRedirect' => \Mcamara\LaravelLocalization\Middleware\LocaleSessionRedirect::class,  
        'localeCookieRedirect' => \Mcamara\LaravelLocalization\Middleware\LocaleCookieRedirect::class,  
        'localeViewPath' => \Mcamara\LaravelLocalization\Middleware\LaravelLocalizationViewPath::class,  

...
    ];

In my route file tenants.php:

Route::group([  
    'prefix' => \LaravelLocalization::setLocale(),  
    'middleware' => ['localeSessionRedirect', 'localeCookieRedirect', 'localizationRedirect']  
], function () use ($namespacePrefixBase) {

...

});

As you mentioned, I moved localizationRedirect to the end of the middleware array, and after further testing, I found that the system center is now functioning properly, allowing access to the default language. However, in the tenant environment, I still encounter the issue of a double 302 redirect.

Additionally, I forgot to mention that my project uses hyn/multi-tenant, as it is a SaaS system divided into two main parts: the system center and the tenants.

Upon further investigation, I found that there might be similarities between my situation and the issue discussed in [https://github.com//issues/912], but they are not identical. I have tried the methods suggested there, but they did not resolve my issue.

In summary,

the configuration above results in two 302 redirects in the tenant environment.
Unable to access the tenants default language

@iwasherefirst2

---

Supplement

When 'hideDefaultLocaleInURL' is set to false,

the default language is not hidden, and this will not result in two 302 redirects, which could cause SEO issues and duplicate content.

When 'hideDefaultLocaleInURL' is set to false,

it will redirect /ja to /, thus avoiding the second 302 redirect. However, this will prevent switching languages based on the browser settings.