why is 401 mapped to unauthenticated instead of unauthorized? #312
              
                Unanswered
              
          
                  
                    
                      daniel-portillo
                    
                  
                
                  asked this question in
                Q&A
              
            Replies: 0 comments
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
        
    
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all, just a qq around this mapping here: https://github.com/apollographql/datasource-rest/blob/main/src/RESTDataSource.ts#L377
This is one of those things that I've always felt makes more sense to be
UNAUTHENTICATEDbut sadly isn't so.https://www.rfc-editor.org/rfc/rfc9110.html#name-401-unauthorized
This mapping mentioned above tripped me up a bit because it seems to go against the spec and the expectation from the client is usually for this code to be
UNAUTHORIZEDjust for historical reasons.Wanted to see how others felt about this and whether it might be something that could be changed. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions