Kong Insomnia returning error when calling GitHub Web Service to decode a Base64 Response to display PDF

[smiller0924]

I have been using Postman for a while to decode a PDF returned to me via another web service as Base64. The Key look up field is a tracking number returned in the same Web Service as the one that I am getting my Base64 encoded PDF. Here is what it looks like in Postman:

I can click the ""html_url": "https://github.com/smiller0924/github-api-document/blob/main/BOL_794862909472.pdf"," and it will take me to my GitHub Page to display my Bill of Lading:

When I try to use Insomnia to same way:

I get the following error:

`* Preparing request to https://api.github.com/repos/smiller0924/github-api-document/contents/BOL_794862909510.pdf

• Current time is 2025-03-24T20:50:25.641Z
• Enable automatic URL encoding
• Using default HTTP version
• Enable timeout of 30000ms
• Enable SSL validation
• Enable cookie sending with jar of 4 cookies
• Connection 15 seems to be dead
• Closing connection 15
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• Hostname in DNS cache was stale, zapped
• Trying 140.82.112.5:443...
• Connected to api.github.com (140.82.112.5) port 443 (Replace Loki with POJSO #16)
• ALPN: offers h2
• ALPN: offers http/1.1
• successfully imported Windows CA store
• TLSv1.0 (OUT), TLS header, Certificate Status (22):
• TLSv1.3 (OUT), TLS handshake, Client hello (1):
• TLSv1.2 (IN), TLS header, Certificate Status (22):
• TLSv1.3 (IN), TLS handshake, Server hello (2):
• TLSv1.2 (IN), TLS header, Finished (20):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, Certificate (11):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, CERT verify (15):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, Finished (20):
• TLSv1.2 (OUT), TLS header, Finished (20):
• TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• TLSv1.3 (OUT), TLS handshake, Finished (20):
• SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
• ALPN: server accepted h2
• Server certificate:
• subject: CN=*.github.com
• start date: Feb 5 00:00:00 2025 GMT
• expire date: Feb 5 23:59:59 2026 GMT
• subjectAltName: host "api.github.com" matched cert's "*.github.com"
• issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo ECC Domain Validation Secure Server CA
• SSL certificate verify ok.
• Using HTTP2, server supports multiplexing
• Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• h2h3 [:method: PUT]
• h2h3 [:path: /repos/smiller0924/github-api-document/contents/BOL_794862909510.pdf]
• h2h3 [:scheme: https]
• h2h3 [:authority: api.github.com]
• h2h3 [authorization: Bearer [REDACTED]]
• h2h3 [content-type: application/json]
• h2h3 [accept: /]
• h2h3 [content-length: 187522]
• Using Stream ID: 1 (easy handle 0x22711919db0)
• TLSv1.2 (OUT), TLS header, Supplemental data (23):

PUT /repos/smiller0924/github-api-document/contents/BOL_794862909510.pdf HTTP/2
Host: api.github.com
authorization: Bearer [REDACTED]
content-type: application/json
accept: /
content-length: 187522

• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• TLSv1.2 (OUT), TLS header, Supplemental data (23):
• TLSv1.2 (OUT), TLS header, Supplemental data (23):

| (64 KB hidden)

• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
• old SSL session ID is stale, removing
• TLSv1.2 (IN), TLS header, Supplemental data (23):
• TLSv1.2 (IN), TLS header, Supplemental data (23):

< HTTP/2 403
< cache-control: no-cache
< content-type: text/html; charset=utf-8
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< x-content-type-options: nosniff
< x-frame-options: deny
< x-xss-protection: 0
< content-security-policy: default-src 'none'; style-src 'unsafe-inline'

• HTTP error before end of send, stop sending

• Received 252 B chunk

• TLSv1.2 (IN), TLS header, Supplemental data (23):

• HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)

• Connection Replace Loki with POJSO #16 to host api.github.com left intact`

I'm not sure why this works in Postman but not Insomnia. If anyone has any ideas I would appreciate the assistance.

Thank you.

[godfrzero]

Hey @smiller0924, could you reach out to us at [email protected]?

[smiller0924]

Vivek, I have opened a case with Insomnia Support. I made sure to include the Discussion Title and Number 8515 in the email. I received an email acknowledging the receipt of my email. I am trying to migrate everything from Postman to Insomnia. This is one of the last things that I need to do in order to complete the migration. Thank you for your assistance on this. Stephen Miller

…

On Mon, Mar 31, 2025 at 8:08 PM Vivek Thuravupala ***@***.***> wrote: Hey @smiller0924 <https://github.com/smiller0924>, could you reach out to us at ***@***.***? — Reply to this email directly, view it on GitHub <#8515 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZZHLVUH7CVCOKJNZMDACCL2XHKJHAVCNFSM6AAAAABZV6A3OSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRYGIZTAMI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[smiller0924]

I wanted to get back to the Insomnia Team about issues that I was having generating a document using the GitHub API. I was able to finally get it to work.

I realized that the variables that I was using to contain my Base64 Response as well as the Tracking number were not the ones being generated in shipment request. They were a hardcoded variable from earlier testing. I modified my scripting to capture the appropriate elements of my reply to capture the Base64 Encoded PDF and Tracking Number. Then fed this two variables into my GitHub call. Voila! It worked!