ctx.req is undefined in Document

[bluelovers]

Bug report

Describe the bug

A clear and concise description of what the bug is.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

class MyDocument extends Document
{

	static async getInitialProps(ctx: DocumentContext)
	{
		console.log(`MyDocument`, `getInitialProps`, this)

		if (1 || typeof window === 'undefined')
		{
			const state = getNextGlobalState();
			state.hostInfo = getNextHost(ctx) ?? state.hostInfo;

			const _ctx = getNextPageContext(ctx);

			console.dir(ctx)
			console.dir(_ctx)

			console.dir(state)
		}

		const initialProps = await Document.getInitialProps(ctx);

		return initialProps
	}

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

System information

• OS: [e.g. macOS, Windows]
• Browser (if applies) [e.g. chrome, safari]
• Version of Next.js: [e.g. 6.0.2]
• Version of Node.js: [e.g. 10.10.0]

Additional context

Add any other context about the problem here.

[jamesmosier]

Hi @bluelovers. _document.js is not the recommended place for code like this. Document is not meant to hold application logic like this. There are also some other caveats](https://nextjs.org/docs/advanced-features/custom-document#caveats) too.

Code like what you have above should be put in _app.js. That will achieve what you are looking for and will run on every page.

[eschaefer]

There are cases where you need server-side cookies to modify the parent html element or body element, for example. This must happen in _document.js and cannot happen elsewhere.

My workaround was to add an empty getServerSideProps call to the appropriate pages/[pagename].js file further down the tree. Then ctx.req in _document.js has the expected headers, cookies, etc. More background here.