Closed liusuyi2021 closed 1 year ago
Hello, it turned out that the specification prescribes to use ETag instead of E-Tag:
https://datatracker.ietf.org/doc/draft-murillo-whep/
So the previous implementation was wrong.
This issue is being locked automatically because it has been closed for more than 6 months. Please open a new issue in case you encounter a similar problem.
Which version are you using?
v1.1.1
Which operating system are you using?
Describe the issue
Description
Describe how to replicate the issue
After updating to version 1.1.1, the whep class of webrtc was unable to obtain an E-Tag. After testing, I found that you changed the E-Tag to ETag after this update, which caused me to stay at 400
Did you attach the server logs?
no
Did you attach a network dump?
no