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
[bug]: PJSIP_RESPONSE_HEADERS function documentation is misleading #230
Labels
Comments
jcolp
added
support-level-core
Functionality with core support level
and removed
triage
labels
Aug 8, 2023
InterLinked1
added a commit
to InterLinked1/asterisk
that referenced
this issue
Aug 9, 2023
The documentation for PJSIP_HEADERS claims that prefix is optional, but in the code it is actually not. However, there is no inherent reason for this, as users may want to retrieve all header names, not just those beginning with a certain prefix. This makes the prefix optional for this function, simply fetching all header names if not specified. As a result, the documentation is now correct. Resolves: asterisk#230 UserNote: The prefix argument to PJSIP_HEADERS is now optional. If not specified, all header names will be returned.
InterLinked1
added a commit
to InterLinked1/asterisk
that referenced
this issue
Aug 9, 2023
The documentation for PJSIP_HEADERS claims that prefix is optional, but in the code it is actually not. However, there is no inherent reason for this, as users may want to retrieve all header names, not just those beginning with a certain prefix. This makes the prefix optional for this function, simply fetching all header names if not specified. As a result, the documentation is now correct. Resolves: asterisk#230 UserNote: The prefix argument to PJSIP_HEADERS is now optional. If not specified, all header names will be returned.
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Aug 14, 2023
The documentation for PJSIP_HEADERS claims that prefix is optional, but in the code it is actually not. However, there is no inherent reason for this, as users may want to retrieve all header names, not just those beginning with a certain prefix. This makes the prefix optional for this function, simply fetching all header names if not specified. As a result, the documentation is now correct. Resolves: #230 UserNote: The prefix argument to PJSIP_HEADERS is now optional. If not specified, all header names will be returned.
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Aug 14, 2023
The documentation for PJSIP_HEADERS claims that prefix is optional, but in the code it is actually not. However, there is no inherent reason for this, as users may want to retrieve all header names, not just those beginning with a certain prefix. This makes the prefix optional for this function, simply fetching all header names if not specified. As a result, the documentation is now correct. Resolves: #230 UserNote: The prefix argument to PJSIP_HEADERS is now optional. If not specified, all header names will be returned.
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Aug 14, 2023
The documentation for PJSIP_HEADERS claims that prefix is optional, but in the code it is actually not. However, there is no inherent reason for this, as users may want to retrieve all header names, not just those beginning with a certain prefix. This makes the prefix optional for this function, simply fetching all header names if not specified. As a result, the documentation is now correct. Resolves: #230 UserNote: The prefix argument to PJSIP_HEADERS is now optional. If not specified, all header names will be returned.
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Aug 14, 2023
The documentation for PJSIP_HEADERS claims that prefix is optional, but in the code it is actually not. However, there is no inherent reason for this, as users may want to retrieve all header names, not just those beginning with a certain prefix. This makes the prefix optional for this function, simply fetching all header names if not specified. As a result, the documentation is now correct. Resolves: #230 UserNote: The prefix argument to PJSIP_HEADERS is now optional. If not specified, all header names will be returned.
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Sep 6, 2023
The documentation for PJSIP_HEADERS claims that prefix is optional, but in the code it is actually not. However, there is no inherent reason for this, as users may want to retrieve all header names, not just those beginning with a certain prefix. This makes the prefix optional for this function, simply fetching all header names if not specified. As a result, the documentation is now correct. Resolves: #230 UserNote: The prefix argument to PJSIP_HEADERS is now optional. If not specified, all header names will be returned. (cherry picked from commit 08e7d77)
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Sep 6, 2023
The documentation for PJSIP_HEADERS claims that prefix is optional, but in the code it is actually not. However, there is no inherent reason for this, as users may want to retrieve all header names, not just those beginning with a certain prefix. This makes the prefix optional for this function, simply fetching all header names if not specified. As a result, the documentation is now correct. Resolves: #230 UserNote: The prefix argument to PJSIP_HEADERS is now optional. If not specified, all header names will be returned. (cherry picked from commit 8be503b)
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Sep 6, 2023
The documentation for PJSIP_HEADERS claims that prefix is optional, but in the code it is actually not. However, there is no inherent reason for this, as users may want to retrieve all header names, not just those beginning with a certain prefix. This makes the prefix optional for this function, simply fetching all header names if not specified. As a result, the documentation is now correct. Resolves: #230 UserNote: The prefix argument to PJSIP_HEADERS is now optional. If not specified, all header names will be returned. (cherry picked from commit 2179082)
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Sep 6, 2023
The documentation for PJSIP_HEADERS claims that prefix is optional, but in the code it is actually not. However, there is no inherent reason for this, as users may want to retrieve all header names, not just those beginning with a certain prefix. This makes the prefix optional for this function, simply fetching all header names if not specified. As a result, the documentation is now correct. Resolves: #230 UserNote: The prefix argument to PJSIP_HEADERS is now optional. If not specified, all header names will be returned. (cherry picked from commit 2179082)
asterisk-org-access-app bot
pushed a commit
that referenced
this issue
Sep 6, 2023
The documentation for PJSIP_HEADERS claims that prefix is optional, but in the code it is actually not. However, there is no inherent reason for this, as users may want to retrieve all header names, not just those beginning with a certain prefix. This makes the prefix optional for this function, simply fetching all header names if not specified. As a result, the documentation is now correct. Resolves: #230 UserNote: The prefix argument to PJSIP_HEADERS is now optional. If not specified, all header names will be returned. (cherry picked from commit 2179082)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Severity
Trivial
Versions
18.16.0
Components/Modules
pjsip, Dialplan
Operating Environment
Debian bullseye/sid, FreePBX
Frequency of Occurrence
None
Issue Description
The documentation for PJSIP_HEADERS describes a parameter called
prefix
and uses the wording "if specified", which heavily implies that the parameter is optional.However, in the actual implementation a zero-length
prefix
is not allowed.Admittedly, it would be more convenient for my use-case if the function worked as described in the documentation (in other words, the parameter is optional and when not provided the function returns all headers). I understand that borders on a feature request, so it would be nice to have the documentation say "required" instead of "if specified".
Relevant log output
Asterisk Issue Guidelines
The text was updated successfully, but these errors were encountered: