JKHeadley/rest-hapi

Support OPTIONS and HEAD verbs

Open

#136 建立於 2018年7月3日

在 GitHub 查看
 (0 留言) (1 反應) (0 負責人)JavaScript (1,181 star) (156 fork)batch import
enhancementhelp wanted

描述

Is your feature request related to a problem? Please describe. For integration with upstream/downstream systems, a model's OPTIONS endpoint might need to be customized, say to allow a different CORS response.

HEAD would complete the support for all "read" verbs. It just needs to return what GET will return, minus the payload.

貢獻者指南

技術棧
javascriptnodejsrest api
領域
backendapi
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Node.jsHTTP methods
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
Investigate the routing mechanism in rest hapi, likely in the source code for generating routes. Add handlers for OPTIONS and HEAD verbs similar to the existing GET handler but with appropriate responses (e.g., empty body for OPTIONS, same headers for HEAD). Check the hapi framework's documentation for default behavior. Implement and test with the existing test suite.