Task #1500
Story #1403: case insensitive parameter support in MultipartRequestResolver
review arch docs to make sure parameters follow the same format (camelText)
Start date:
Due date:
% Done:
100%
Milestone:
Product Version:
*
Story Points:
Sprint:
History
#1 Updated by Rob Nahf about 13 years ago
- Assignee changed from Rob Nahf to Dave Vieglais
#2 Updated by Dave Vieglais almost 13 years ago
- Status changed from New to In Progress
#3 Updated by Dave Vieglais almost 13 years ago
- Status changed from In Progress to Closed
Docs updated to be clear. The outcome is that case of parameter names and values should be preserved. This is especially important on the request generator side as the server implementation may choose to reject a request with malformed parameter names (e.g. getLogRecords called with a parameter named "fromdate" instead of "fromDate"). This approach is taken to reduce the complexity of implementation of both server and clients (i.e., reducing the number of special cases to be considered).
This applies to both parameters in URLs and parameter names in MIME multiart-mixed encoded bodies.
