Weird issue with URL parsing

[gizbo]

Hello guys,

I have 3 languages: en, fr, and es. The translations work fine using ngx-translate, and the URLs are all getting localized and everything. However, if I try entering a Spanish URL, it doesn't work at all and redirects to the default 404 page in English. French and English seem to be the only ones supported. Do I have to explicitly register the prefixes ['en', 'es', 'fr']?

Thanks so much.

[neverlose-lv]

I have similar problem after updating my project to new Angular version the the new build system.
Earlier - I did not have such problems.
I believe this plugin seems not to be working well with the recent Angular version. (with SSR).
It seems that the request object nor the location path are not defined on the very first query. Then happens 302 redirect to the default language. And the values are populated.
I have tried different approaches with no success.

[SrgSteak]

Hi there! I've recently updated a project of mine to AngularV19, with SSR using the new
"@angular-devkit/build-angular:application" builder.

In case you're using this builder as well, you should be able to find in your output folder for the server build a file called "angular-app-manifest".

What angular does now on server, is that it checks the content of this file for matching routes before even booting into angular. My assumption about your app @gizbo and please correct me if I'm wrong, is that your default language is english, so the "routes:" section in the "angular-app-manifest" has a list of english routes and no spanish ones.

What in this case happens is:
browser requests (localhost/es) -> node server gets the request -> angular checks the manifest routes, finds no match, uses the /** -> 404 response without even booting your angular app completely.

Proposed solutions:

A (@neverlose-lv)

• replace the routes: [] section with routes: [{"renderMode": 0, "route": "/**"}] after build
• run node. Your requests are now handled by ssr as expected

I'm currently doing this. I've also overwritten a few functions on my LocalizeParser, especially the getLocationLang(url?: string): string to retrieve the requested language from my request_context

B
@gilsdav, @ruizmarc (I've seen you on the looking for maintainers Issue)

During the build step, the translate router should spit out a list of all supported languages for the router so that the "angular-app-manifest" routes section contains all translated routes (including their given renderOption).
I wasn't too keen on taking the bundle or the angular builder apart on how to achieve that or if you've run into this issue already.

I hope this comment is helpful and I'll be able to help/clarify in case something is unclear.