camtauxe opened a new pull request #623:
URL: https://github.com/apache/couchdb-documentation/pull/623


   <!-- Thank you for your contribution!
   
        Please file this form by replacing the Markdown comments
        with your text. If a section needs no action - remove it.
   
        Also remember, that CouchDB uses the Review-Then-Commit (RTC) model
        of code collaboration. Positive feedback is represented +1 from 
committers
        and negative is a -1. The -1 also means veto, and needs to be addressed
        to proceed. Once there are no objections, the PR can be merged by a
        CouchDB committer.
   
        See: http://couchdb.apache.org/bylaws.html#decisions for more info. -->
   
   ## Overview
   
   <!-- Please give a short brief for the pull request,
        what problem it solves or how it makes things better. -->
   
   The instructions for creating the HMAC token (recommended for proxy 
authentication) aren't specific enough for developers to actually create a 
token from a username and secret. This PR clarifies the instructions, adds an 
example (using openssl) of creating the token and then adds it to the example 
HTTP request.
   
   ## Testing recommendations
   
   <!-- Describe how we can test your changes.
        Does it provides any behaviour that the end users
        could notice? -->
   - Make sure documentation and syntax highlighting look okay on webpage
   - Check that the example openssl command works and produces the same HMAC
   
   ## Checklist
   
   - [ ] Update 
[rebar.config.script](https://github.com/apache/couchdb/blob/main/rebar.config.script)
 with the commit hash once this PR is rebased and merged
   <!-- Before opening the PR, consider running `make check` locally for a 
faster turnaround time -->
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to