Repository: next.js
Issue: OG Image tags don't get scraped by FB for dynamic routes (appdir)
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

 Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.2.0: Fri Nov 11 02:03:51 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.14.0
      npm: 8.3.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.1.1-canary.1
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

### Which area(s) of Next.js are affected? (leave empty if unsure)

Head component/file (next/head / head.js)

### Link to the code that reproduces this issue

https://github.com/saarnav890/ogImageIssue

### To Reproduce

To reproduce, try to run the FB sharing debugger, https://developers.facebook.com/tools/debug/?q=https%3A%2F%2Fog-image-issue.vercel.app%2F. 
(results in a good image)


Then, run the same debugger but with anything else as the /[slug], for instance, https://og-image-issue.vercel.app/something.

https://developers.facebook.com/tools/debug/?q=https%3A%2F%2Fog-image-issue.vercel.app%2Fsomething
(results in a 500 internal server error)



Additionally, according to https://developers.facebook.com/docs/sharing/webmasters/crawler/ you can run 

curl -v --compressed -H "Range: bytes=0-524288" -H "Connection: close" -A "facebookexternalhit/1.1 (+http://www.facebook.com/externalhit_uatext.php)" https://og-image-issue.vercel.app/

to get the proper response, 

but running

curl -v --compressed -H "Range: bytes=0-524288" -H "Connection: close" -A "facebookexternalhit/1.1 (+http://www.facebook.com/externalhit_uatext.php)" https://og-image-issue.vercel.app/something

results in a 500 internal server error. 

However, if you just remove the range header, the dynamic content works:

curl -v --compressed -H "Connection: close" -A "facebookexternalhit/1.1 (+http://www.facebook.com/externalhit_uatext.php)" https://og-image-issue.vercel.app/something



### Describe the Bug

The FB crawler works perfectly fine when crawling statically generated pages. However, when trying to crawl dynamically generated pages, it gives a 500 internal server error. 


**This is the expected response for the index page:**

<img width="792" alt="image" src="https://user-images.githubusercontent.com/63823257/210153135-1b57545f-59b7-4bd8-a07f-3f88d7253140.png">

**This is the response for anything dynamically rendered:**

<img width="821" alt="image" src="https://user-images.githubusercontent.com/63823257/210153124-7417e6b5-06ed-48d5-a79e-652ac3aaa98c.png">



### Expected Behavior

The crawler should return the same image for both the index page and any slug page, however, this is not happening. When I try this with other meta tag simulators such as https://en.rakko.tools/tools/9/ both work perfectly fine. Because of this, I think it has something to do with the range header. 

### Which browser are you using? (if relevant)

Version 108.0.5359.124 (Official Build) (arm64)

### How are you deploying your application? (if relevant)

Vercel