Feature Request
Are there plans to implement Procative Auth?
According to claude.ai:
The code is not implementing proactive authorization because it only handles authentication reactively - after receiving a 401/407 challenge from the server.
The code should check if credentials exist from a previous authentication and include the Authorization header in the initial REGISTER request.
Why It Matters:
Without proactive auth: Every registration requires 2 round trips (initial request → 401 → authenticated request)
With proactive auth: Subsequent registrations use 1 round trip (authenticated request → 200 OK) by reusing cached credentials
This is particularly important for re-registrations since the code already has the nonce and realm from the previous authentication. The current implementation wastes network resources by forcing a challenge-response every time, even though it could preemptively include credentials.
Feature Request
Are there plans to implement Procative Auth?
According to claude.ai:
The code is not implementing proactive authorization because it only handles authentication reactively - after receiving a 401/407 challenge from the server.
The code should check if credentials exist from a previous authentication and include the Authorization header in the initial REGISTER request.
Why It Matters:
Without proactive auth: Every registration requires 2 round trips (initial request → 401 → authenticated request)
With proactive auth: Subsequent registrations use 1 round trip (authenticated request → 200 OK) by reusing cached credentials
This is particularly important for re-registrations since the code already has the nonce and realm from the previous authentication. The current implementation wastes network resources by forcing a challenge-response every time, even though it could preemptively include credentials.