@vercel/next matches exact route match for dynamic pages

[Timer]

Bug report

Describe the bug

@vercel/next matches exact paths for dynamic routes, successfully invoking a lambda when the page is meant to be static.

To Reproduce

View success instead of 404 here.

https://test-direct-access.vercel.app/_src

❯ httpstat https://test-direct-access.vercel.app/test/[slug]

Connected to 76.76.21.21:443

HTTP/2.0 200 OK
Server: Vercel
Age: 0
Cache-Control: public, max-age=0, must-revalidate
Content-Type: text/html; charset=utf-8
Date: Tue, 11 Aug 2020 14:05:05 GMT
Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
X-Nextjs-Page: /test/[slug]
X-Vercel-Cache: MISS
X-Vercel-Id: cle1::sfo1::lhkc7-1597154704606-04600048d451

Body discarded

  DNS Lookup   TCP Connection   TLS Handshake   Server Processing   Content Transfer
[      1ms  |          36ms  |        196ms  |            811ms  |             6ms  ]
            |                |               |                   |                  |
   namelookup:1ms            |               |                   |                  |
                       connect:38ms          |                   |                  |
                                   pretransfer:235ms             |                  |
                                                     starttransfer:1047ms           |
                                                                                total:1053ms  

Expected behavior

The page should 404.

[ijjk]

Closing per #33808

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.