Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stale Nonce #28

Closed
buendiya opened this issue Jul 1, 2020 · 2 comments
Closed

Stale Nonce #28

buendiya opened this issue Jul 1, 2020 · 2 comments

Comments

@buendiya
Copy link
Contributor

buendiya commented Jul 1, 2020

Hi
According to https://tools.ietf.org/html/rfc5389#page-27.

If the response is an error response with an error code of 438 (Stale
Nonce), the client MUST retry the request, using the new NONCE
supplied in the 438 (Stale Nonce) response.

I can't find implementation about this in code.

I am using coturn as turnserver. The default nonce lifetime is 600 secs. It will raise a Stale Nonce TransactionFailed after 600 secs.

@jlaine
Copy link
Collaborator

jlaine commented Jan 26, 2021

Is there a public server where I can test this?

@jlaine
Copy link
Collaborator

jlaine commented Jan 26, 2021

From reading the RFC I'm not sure I can tell the difference between the handling of 401 or 438 status codes. It seems in both cases the NONCE and REALM attributes need to be updated?

I am tempted to handle both cases here:

https://github.com/aiortc/aioice/blob/main/src/aioice/turn.py#L87

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

No branches or pull requests

2 participants