ARC not showing results - "The response is a binary data."

[thezoggy]

• Application version: 16.0.1 / 17.0.3-beta
• Operating System (Platform and Version): macos 10.15.7

Expected Behavior
Should show the result of the API call.

Actual behavior
ARC thinks the response is binary. - "The response is a binary data."
These calls did work previously and were in my ARC history. Was on 17.0.3-beta when I ran into it, went back to 16.0.1 and it is no longer working there either. Testing with curl I can confirm it is just text and looks fine.

To Reproduce
Sent normal rest call using token..

Screenshots
not needed

Additional Information

testing via cli:

#curl -v "https://<site>/endpoint/" -H "X-Arbux-APIToken: xxx"
*   Trying 2001:418:<removed>...
* TCP_NODELAY set
* Connected to detect-lab.nst.gin.ntt.net (2001:418:<removed>) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: CN=*.<removed>
*  start date: Dec  9 00:00:00 2019 GMT
*  expire date: Feb  6 12:00:00 2022 GMT
*  subjectAltName: host "<removed>" matched cert's "*.<removed>"
*  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=RapidSSL RSA CA 2018
*  SSL certificate verify ok.
> GET /endpoint/ HTTP/1.1
> Host: <removed>
> User-Agent: curl/7.64.1
> Accept: */*
> X-Arbux-APIToken: xxx
> 
< HTTP/1.1 200 OK
< Date: Tue, 14 Dec 2021 22:59:14 GMT
< Server: Apache
< X-Frame-Options: SAMEORIGIN
< Content-Security-Policy: default-src 'self' 'unsafe-inline' 'unsafe-eval'
< X-Content-Type-Options: nosniff
< Strict-Transport-Security: max-age=1261440000
< Content-Length: 443633
< Cache-Control: max-age=0, private, must-revalidate
< P3P: policyref="/w3c/p3p.xml", CP="NOI DSP COR TAIa OUR NOR UNI"
< Content-Type: application/vnd.api+json
< Via: 1.1 127.0.0.1
< Vary: Accept-Encoding
< 
{
  "data": [
      {
      "attributes": {
        "ip_version": 4, 
...

[jarrodek]

Hi,

Thank you for the issue report. It has to do with the application/vnd.api+json mime type reported back by the API. ARC has a rule to render anything that starts with application/vnd as binary. Obviously this is an error on my side.
I corrected this in: https://github.com/advanced-rest-client/base/commit/66f734de838480d53a1831bb6f4e7a3eee2d226b
When it all goes through the CI I'll release the new beta with the fix.

I won't be able to update the 16.x release for that.

[thezoggy]

thanks!

[jarrodek]

I just released the 17.0.4-beta version with the fix with this issue. You can try it to confirm the fix.

[thezoggy]

just d/led 17.0.4-beta and tested and can confirm all is good now. thanks again!