Combined use of cookie chunking and combining middleware

[Tim0401]

Prior to v4.3.0, we implemented Combining middleware by referring to the following documents and examples.
https://github.com/auth0/nextjs-auth0/blob/main/EXAMPLES.md#combining-middleware

nextjs-auth0/examples/with-next-intl/middleware.ts

Lines 20 to 39 in bf35b96

	// Combine headers from authResponse (from auth0.middleware) and intlRes (from intlMiddleware).
	// If authResponse contains 'x-middleware-next' (signaling Next.js to proceed to the page),
	// but intlRes is a response that should terminate the request chain (like a redirect or an error),
	// we must NOT copy 'x-middleware-next' from authResponse. Doing so would override
	// intlRes's decision to stop the request.
	for (const [key, value] of authResponse.headers) {
	if (key.toLowerCase() === 'x-middleware-next') {
	// Check if intlRes is a redirect (3xx status code) or an error (4xx, 5xx status code).
	const isIntlResponseTerminating = intlRes.status >= 300;
	if (isIntlResponseTerminating) {
	// If intlRes is already redirecting or returning an error,
	// do not copy 'x-middleware-next' from authResponse.
	// This allows intlRes's redirect/error to take effect.
	continue;
	}
	}
	// For all other headers, or if 'x-middleware-next' can be safely copied,
	// set them on intlRes. This ensures session cookies from authResponse are preserved.
	intlRes.headers.set(key, value);
	}

After cookie chunking caused cookies to be split, we noticed that the authentication state was not retained.
Upon closer inspection, we found that some of the chunked session cookies were not being stored as cookies.

I noticed that the authResponse in example contains multiple set-cookie headers, so I solved this by using headers.append instead of headers.set.

  // add any headers from the auth middleware to the response
  for (const [key, value] of authResponse.headers) {
    // Only copy 'x-middleware-next' if the custom middleware response intends to proceed.
    if (key.toLowerCase() === 'x-middleware-next' && !shouldProceed) {
      continue; // Skip copying this header if we are blocking/redirecting
    }
    someOtherResponse.headers.append(key, value)
  }

Has anyone encountered a similar event or tried a better solution?