Send the osTicket ticket text raw after the data: prefix, with no encoding
Percent-encoding put "%20" in every space of a real ticket, and the base64 that replaced it arrived as base64. osTicket (Format::parseRfc2397, via ApiJsonDataParser::fixup) takes the message's type from the "data:" prefix and uses everything after the first comma exactly as it is, decoding nothing; its own documented example is plain text after the comma. The text is now sent raw (JSON takes care of quotes and line breaks; later commas are fine, since only the first one splits). The test now mimics that parsing -- split at the first comma, decode nothing -- and requires the text to arrive exactly as written; it fails if percent-encoding or base64 comes back. The stand-in server in the earlier test had decoded the encoding, which is why neither mistake was caught. INTEGRATIONS.md says what happened and that it hasn't been re-checked against a real osTicket. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
5072cee519
commit
5386c1abe7
3 files changed
+15
-12
No files matched your search
+5
-4
@@ -164,10 +164,11 @@ the dashboard views themselves load fine.
|
||||
here is yours to close in osTicket.
|
||||
- **Only partly verified against a real osTicket.** It was built from osTicket's published API documentation and
|
||||
tested against a stand-in server that checks what is sent (the key header, the JSON fields, the message encoding,
|
||||
and how each answer — created, refused key, bad request, redirect — is handled). The first test ticket sent to a
|
||||
real osTicket arrived with every space shown as `%20`: osTicket takes the message from a `data:` URL but does not
|
||||
decode percent-encoding, so the message is now sent as base64, which it does decode (not yet re-checked against a
|
||||
real osTicket). If osTicket rejects a ticket, "Send a test ticket" shows the reason it gave.
|
||||
and how each answer — created, refused key, bad request, redirect — is handled). Tickets sent to a
|
||||
real osTicket first arrived with every space shown as `%20`, then as base64: osTicket takes the message's type from a
|
||||
`data:` prefix but uses everything after the first comma exactly as it is, decoding nothing (its source and its own
|
||||
documented example agree). The text is now sent raw after the prefix (not yet re-checked against a real osTicket). If
|
||||
osTicket rejects a ticket, "Send a test ticket" shows the reason it gave.
|
||||
|
||||
### phpIPAM
|
||||
|
||||
|
||||
Reference in new issue
Block a user