Skip to content

Latest commit

 

History

History
39 lines (27 loc) · 1.26 KB

README.md

File metadata and controls

39 lines (27 loc) · 1.26 KB

Custom server example

The HTTP/1.1 specification says - if charset is not set in the http header then the browser defaults use ISO-8859-1. For languages like Polish, Albanian, Hungarian, Czech, Slovak, Slovene, there will be broken characters encoding from SSR.

You can overwrite Content-Type in getInitialProps. But if you want to handle it as a server side concern, you can use this as an simple example.

How to use

Using create-next-app

Execute create-next-app with npm or Yarn to bootstrap the example:

npm init next-app --example custom-charset custom-charset-app
# or
yarn create next-app --example custom-charset custom-charset-app

Download manually

Download the example:

curl https://codeload.github.com/zeit/next.js/tar.gz/canary | tar -xz --strip=2 next.js-canary/examples/custom-charset
cd custom-charset

Install it and run:

npm install
npm run dev
# or
yarn
yarn dev

Deploy it to the cloud with ZEIT Now (Documentation).