You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Customer noticed that their function, which differentiates POST handling from GET handling, when used on a site with prerendering configured, translates POST to GET which of course broke the function.
I think we MUST handle POST-as-GET for facebook's tendency to use POST to fetch content and that being most of the point of prerendering, but I think we need not transform it for other services, as a customer demonstrated in https://netlify.zendesk.com/agent/tickets/16082 which has a good repro setup.
The text was updated successfully, but these errors were encountered:
Observed the POST from the webhook logged as a GET with 'user-agent': 'Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/74.0.3729.108 Safari/537.36 Prerender (+https://github.com/prerender/prerender)'
Turned prerender off and observed the same behavior, which was unexpected. Turned prerender back on.
adding this to the traffic & delivery platform board; if that turns out to be the wrong place, please at mention me and remove it from there so I can try to find a better place (I am not sure if it is really a bug in the prerender service where I filed it - I think it might be a proxy bug since we proxy to prerender? Advice sought :))
If you remove it from that board because it isn't yours, and don't say something about doing so, it will get lost and that would be sad.
Customer noticed that their function, which differentiates POST handling from GET handling, when used on a site with prerendering configured, translates POST to GET which of course broke the function.
I think we MUST handle POST-as-GET for facebook's tendency to use POST to fetch content and that being most of the point of prerendering, but I think we need not transform it for other services, as a customer demonstrated in https://netlify.zendesk.com/agent/tickets/16082 which has a good repro setup.
The text was updated successfully, but these errors were encountered: