Content Negotiation logic possibly incorrect...?

[raphaklaus]

Hello! First of all, thanks for this amazing tool. You guys have been doing an incredible job!

According to this section of the documentation: https://kit.svelte.dev/docs/routing#server-content-negotiation

If the Accept header is text/html execute a browser request, otherwise, the request is going to hit the respective function inside +server.ts.

It works perfectly until you have your site requested by a facebookbot/twitterbot/whateverbot that is going to send an arbitrary Accept value, such as */*, image/webp. Because it's not a text/html it tries to call an HTTP verb-like middleware, but since it doesn't exist a 405 Method not allowed is returned. By default this behavior makes websites' SEO capabilities to do not work, requiring some configuring on src/hooks.server.ts.

To me, it's far-fetched to infer that an arbitrary (or even empty) Accept header should be interpreted as a server call.