aws-amplify / aws-amplify/amplify-hosting

Support i18n for Nuxt like you did for NextJs

Open
#3,954 1 comment 2 reactions 0 assignees View on GitHub
feature-request
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have removed any sensitive information from my code snippets and submission.

### Amplify Hosting feature

Custom headers, SSR

### Is your feature request related to a problem? Please describe:

Nuxt have the same problem that you solved for NextJs:
https://github.com/aws-amplify/amplify-hosting/issues/3320

### Describe how you'd like this feature to work

Please make sure that also for Nuxtjs applications Cloudfront is forwarding the accept-language header to the origin server

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the related issue #3320 and the Amplify Hosting path for Nuxt SSR applications. Trace where CloudFront request headers are configured, then verify that the accept-language header reaches the origin for Nuxt deployments. Done means Nuxt applications receive the forwarded header as Next.js applications do.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, nuxtjs
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.