Can't get protocol in server-side rendering
See original GitHub issueHi All!
My question is i need to get origin dynamically,
I try req.headers
and I got:
Yes!, I got host, but I also need the protocol, which needs to concat with host to create new api path. I browsed All req properties but I got nothing. Have any good idea? thx a lot!
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Server-side rendering - Apollo GraphQL Docs
Server -side rendering (SSR) is a performance optimization for modern web apps. It enables you to render your app's initial state to raw...
Read more >Nextjs - Cannot get url prarams(query) on server side rendering
So im trying to get req query aka GET params from the url into server side rendering for basicly validation and / login...
Read more >What is server-side rendering and how does it improve site ...
Server -side rendering ensures that website content appears quickly, without first having to download and run application code.
Read more >Headless Chrome: an answer to server-side rendering JS sites
const {html, ttRenderMs} = await ssr(`${req.protocol}://${req.get('host') ...
Read more >Next.js Framework and the Server-Side Rendering method
In 2014 Google announced that it will rank only the sites sending data via the HTTPS protocol. To this end, the website needs...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s safe to assume it’s always
http
and the SSL termination has to be done by a reverse proxy like Nginx. These set theX-Forwarded-Proto
header which you could use.Well that’s my bad!