-
Notifications
You must be signed in to change notification settings - Fork 166
Open
Labels
Element: HTTPIssues related to HTTP handling, TIdHTTP, TIdHTTPServer, TIdHTTPProxyServer, etcIssues related to HTTP handling, TIdHTTP, TIdHTTPServer, TIdHTTPProxyServer, etcStatus: PendingIssue is pending external update or releaseIssue is pending external update or releaseType: EnhancementIssue is proposing a new feature/enhancementIssue is proposing a new feature/enhancement
Milestone
Description
Some REST APIs, like POS systems such as SmartPay SmartConnect, use PUT instead of POST for some commands, but still require the request body to be in application/x-www-webform-urlencoded format. To make this easier to work with, TIdHTTP should expose a TStrings overload of the Put() method to call SetRequestParams(), mimicking what the Post() method does. Maybe even move the SetRequestParams() logic into DoRequest() directly, allowing the Source object to be either a TStrings or a TStream, and encoding accordingly.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Element: HTTPIssues related to HTTP handling, TIdHTTP, TIdHTTPServer, TIdHTTPProxyServer, etcIssues related to HTTP handling, TIdHTTP, TIdHTTPServer, TIdHTTPProxyServer, etcStatus: PendingIssue is pending external update or releaseIssue is pending external update or releaseType: EnhancementIssue is proposing a new feature/enhancementIssue is proposing a new feature/enhancement
Type
Projects
Status
In review