Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update TIdHTTP to support RFC 7617 charset parameter for BASIC authentication #126

Closed
rlebeau opened this issue Apr 6, 2017 · 0 comments
Closed

Update TIdHTTP to support RFC 7617 charset parameter for BASIC authentication #126

rlebeau opened this issue Apr 6, 2017 · 0 comments
Assignees
@rlebeau
Labels
Element: HTTP Issues related to HTTP handling, TIdHTTP, TIdHTTPServer, TIdHTTPProxyServer, etc Status: Fixed Issue has been fixed, no further work needed Type: Enhancement Issue is proposing a new feature/enhancement

Comments

@rlebeau
Copy link
Member

rlebeau commented Apr 6, 2017 •
edited
Loading

RFC 7617 adds a "charset" parameter to the HTTP WWW-Authentication header for BASIC authentication to specify the charset used for encoding the username/password before applying base64.
@rlebeau rlebeau added Type: Enhancement Issue is proposing a new feature/enhancement Element: HTTP Issues related to HTTP handling, TIdHTTP, TIdHTTPServer, TIdHTTPProxyServer, etc labels Apr 6, 2017
@rlebeau
Copy link
Member Author

rlebeau commented Apr 6, 2017 •
edited
Loading

Support for the "charset" attribute has been added to TIdBasicAuthentication in SVN rev 5321. This only applies to client-side authentication in TIdHTTP. Server-side support in TIdHTTPServer has not been implemented yet. Opening new ticket #469 for that.

@rlebeau rlebeau self-assigned this Apr 6, 2017
@rlebeau rlebeau changed the title Add support for RFC 7617 Add support for RFC 7617 charset parameter Aug 6, 2021
@rlebeau rlebeau changed the title Add support for RFC 7617 charset parameter Update TIdHTTP to support RFC 7617 charset parameter for BASIC authentication Apr 25, 2023
@rlebeau rlebeau added the Status: Fixed Issue has been fixed, no further work needed label Apr 25, 2023
@rlebeau rlebeau closed this as completed Apr 25, 2023
@rlebeau rlebeau mentioned this issue Apr 28, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rlebeau rlebeau

Labels
Element: HTTP Issues related to HTTP handling, TIdHTTP, TIdHTTPServer, TIdHTTPProxyServer, etc Status: Fixed Issue has been fixed, no further work needed Type: Enhancement Issue is proposing a new feature/enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rlebeau