Skip to content

fix: distinguish between 401 and 403 HTTP error codes#24

Merged
wcole1-godaddy merged 1 commit intogodaddy:mainfrom
cblecken-godaddy:distinguish-http-errors
Apr 13, 2026
Merged

fix: distinguish between 401 and 403 HTTP error codes#24
wcole1-godaddy merged 1 commit intogodaddy:mainfrom
cblecken-godaddy:distinguish-http-errors

Conversation

@cblecken-godaddy
Copy link
Copy Markdown
Collaborator

Summary

  • Separates handling of 401 (authentication) and 403 (authorization) errors
  • 401: "Authentication failed. Run 'godaddy auth login'."
  • 403: "Access denied. You may not have permission for this operation in the current environment."

This provides clearer guidance to users - authentication failures prompt re-login, while authorization failures indicate a permissions issue.

Test plan

  • Trigger a 401 error (expired/invalid token) and verify message
  • Trigger a 403 error (valid token, insufficient permissions) and verify message

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

- 401: Authentication failed - prompts user to run 'godaddy auth login'
- 403: Access denied - indicates permission issue in current environment

This provides clearer guidance to users when they encounter authorization vs authentication issues.
@wcole1-godaddy wcole1-godaddy merged commit 2a02d04 into godaddy:main Apr 13, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants