Fix duplicate set-cookie headers #44
                
     Open
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Currently, this will result in 2 set-cookie headers. One in
Headersand one inCookies.Without this fix, the included test fails on
assert.Equal(t, 1, len(e.Headers))(has 2,Content-Type+Set-Cookie)Also @wolfeidau @tj the tests are passing, though like in #39, I'm guessing this will fail with AWS Build/Semaphore - are these build processes broken? Maybe we can just disable them and just use Actions to run the tests.