Markdown for Agents returns 406

[collimarco]

Existing documentation URL(s)

We have enabled "Markdown for Agents" for the /docs path as described here:

https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/

In particular we have enabled the rule for the path /docs or paths that start with /docs/.

However when we try to request the docs in markdown or a specific docs path in markdown, we get a 406 response.

For example:

curl -v -H "Accept: text/markdown" https://pushpad.xyz/docs/pushpad_pro_getting_started

Returns 406.

What changes are you suggesting?

Please clarify in the documentation what can cause that error.

Additional information

No response

[kodster28]

There's already a section on the page describing limitations (which is when it might respond with a 406). Namely, page size above 2 MB.

https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/#limitations

[collimarco]

@kodster28 I already read that section. Nothing can be applied to this case... Our pages are definitely smaller than 2MB.

[kodster28]

Few internal threads, seems like the 406 is being returned by your origin itself (not Cloudflare).

curl -v -H "Accept: text/markdown,text/html" https://pushpad.xyz/docs/pushpad_pro_getting_started

This will work because it gives the origin a chance to return something the client accepts (text/html), and then the content -converter module sees the client prefers markdown and converts.

[collimarco]

Thanks, you found the culprit.

However it is normal that origin server returns 406 for text/markdown... the website supports only HTML. That's why we have enabled the Cloudflare Markdown feature... If the origin website supported markdown, then there was no reason to use the Cloudflare feature.

Probably Cloudflare should add the text/html fallback automatically to the headers when text/markdown is requested and the Markdown for Agents is enabled.

[collimarco]

Another issue that I see is that the docs navigation is removed in the markdown version (but this is probably a separate topic).

Considering all the above reasons, we are going to pause this feature for now.

[kodster28]

Forwarded along this feedback to the team, but understand why you're pausing for now.
(also heard other feedback along the vein of customizing the content that's returned / excluded, though no immediate plans here)

Closing out this issue as it's more related to feedback on the product (and less about our docs repo specifically).