Here is a change set which consists of two patches for mod_auth_custom_http.
The first one sets "Content-Type" header of the request to "application/json". Before, while json was sent as a request body, the content type was web form. Some web frameworks need to implement hackish solutions to support that and it is more consistent to set the content type header to json, so that the body contents conform this header. With the header set it is easier to implement an auth service to work with the mod_auth_custom_http. The second patch implements support for HTTPS protocol. It relies on "ssl.https" module for that. It works pretty much the same way as for HTTP. The schema part of the URL is searched for "https://"; beginning and if it there it uses "ssl.https.request" and if it's not it uses the old "socket.http.request". It will unlikely break the old HTTP support so I think it is safe to merge. -- You received this message because you are subscribed to the Google Groups "prosody-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to prosody-dev+unsubscr...@googlegroups.com. To post to this group, send email to prosody-dev@googlegroups.com. Visit this group at https://groups.google.com/group/prosody-dev. For more options, visit https://groups.google.com/d/optout.
auth-custom-http-improvements.hg
Description: Binary data
signature.asc
Description: OpenPGP digital signature
