Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Image unknown errors. #70129

Closed
omerman opened this issue Sep 15, 2024 · 2 comments
Closed

Image unknown errors. #70129

omerman opened this issue Sep 15, 2024 · 2 comments
Labels
bug Issue was opened via the bug report template.

Comments

@omerman
Copy link

omerman commented Sep 15, 2024

Link to the code that reproduces this issue

https://github.com/omerman/next13-unmounts-reproduction/

To Reproduce

Not sure.

Maybe related to #22329

Current vs. Expected behavior

[15.09.2024 18:44.03.821] [ERROR] Error: Invalid accept header
at s.parse ([path_to_next_modules]/@hapi/accept/index.js:1:3083)
at t.selections ([path_to_next_modules]/@hapi/accept/index.js:1:2564)
at t.selection ([path_to_next_modules]/@hapi/accept/index.js:1:2425)
at t.mediaType ([path_to_next_modules]/@hapi/accept/index.js:1:2085)
at getSupportedMimeType ([path_to_next_modules]/image-optimizer.js:179:44)
at ImageOptimizerCache.validateParams ([path_to_next_modules]/image-optimizer.js:436:26)
at NextNodeServer.handleNextImageRequest ([path_to_next_modules]/next-server.js:167:58)
at Server.normalizeAndAttachMetadata ([path_to_next_modules]/base-server.js:292:39)
at NextNodeServer.handleRequestImpl ([path_to_next_modules]/base-server.js:848:39)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async invokeRender ([path_to_next_modules]/router-server.js:183:21)
at async handleRequest ([path_to_next_modules]/router-server.js:360:24)
at async requestHandlerImpl ([path_to_next_modules]/router-server.js:384:13)
at async Server.requestListener ([path_to_next_modules]/start-server.js:142:13) {
data: null,
isBoom: true,
isServer: false,
output: {
statusCode: 400,
payload: {
statusCode: 400,
error: 'Bad Request',
message: 'Invalid accept header'
},
headers: {}
}
}

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 1.22.19
  pnpm: 8.14.1
Relevant Packages:
  next: 15.0.0-canary.155 // There is a newer canary version (15.0.0-canary.156) available, please upgrade! 
  eslint-config-next: 14.2.3
  react: 19.0.0-rc-206df66e-20240912
  react-dom: 19.0.0-rc-206df66e-20240912
  typescript: 5.2.2
Next.js Config:
  output: N/A
 ⚠ There is a newer canary version (15.0.0-canary.156) available, please upgrade! 
   Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
   Read more - https://nextjs.org/docs/messages/opening-an-issue

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

Other (Deployed)

Additional context

No response

@omerman omerman added the bug Issue was opened via the bug report template. label Sep 15, 2024
@samcx
Copy link
Member

samcx commented Sep 16, 2024

@omerman Where are you trying to deploy this? Was not able to replicate this on Vercel.

@omerman
Copy link
Author

omerman commented Sep 17, 2024

@samcx My app is deployed to an IIS server, using reverse proxy. snippet from web.release config:

          <rule name="ReverseProxyInboundRule2" stopProcessing="true">
		<match url="^dashboard(/)?(.*)" />
		<action type="Rewrite" url="http://localhost:4000/{R:0}" />
		<serverVariables>
			<set name="HTTP_X_FORWARDED_HOST" value="{HTTP_HOST}" />
		</serverVariables>
	</rule>

@vercel vercel locked and limited conversation to collaborators Sep 17, 2024
@samcx samcx converted this issue into discussion #70198 Sep 17, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
bug Issue was opened via the bug report template.
Projects
None yet
Development

No branches or pull requests

2 participants