We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
I have checked the HEP packets content and confirmed that the headers values equal SIP messages. Screenshot with one one-space chart after : attached
:
But when the same message is presented in the web interface, there are two space characters.
Sometimes these extra charaiters are misleading and will be fine to present headers with the same format in original SIP message.
The text was updated successfully, but these errors were encountered:
This seems just related to the styling which attempts to make the SIP header bold. It shouldn't add extra spacing indeed.
Sorry, something went wrong.
RFbkak37y3kIY
Successfully merging a pull request may close this issue.
I have checked the HEP packets content and confirmed that the headers values equal SIP messages.
Screenshot with one one-space chart after
:
attachedBut when the same message is presented in the web interface, there are two space characters.
Sometimes these extra charaiters are misleading and will be fine to present headers with the same format in original SIP message.
The text was updated successfully, but these errors were encountered: