Repository navigation
fix(proxy): match the route verb like HaRP - #1144
Conversation
Signed-off-by: Oleksandr Piskun <oleksandr2088@icloud.com>
b1bde3c to
c6f1660
Compare
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Priority: ➖ Normal Merge Risk: ⚪ Minimal · up to
|
Signed-off-by: Oleksandr Piskun <oleksandr2088@icloud.com>
AppAPI's ExApp proxy reads the
<verb>of a route with a substring check and refusesHEADunless a route lists it, while HaRP (nextcloud/HaRP#149) reads the verb as a list of methods and acceptsHEADwhereverGETis listed. So the same ExApp answered differently depending on whether a request went through the proxy or through HaRP: aHEADto a page (link previews, monitors) got 404 from the proxy, and a verb written asGETPOSTmatched both GET and POST on the proxy but neither on HaRP.Changes
GET;POST, no longer matches by substring, so such a request is decided by a later route of the path, as on HaRP. No published ExApp writes its verbs like that.HEADis accepted on routes that listGET. Nextcloud already routesHEADto the proxy's GET action, which forwards it as GET.