Skip to content
This repository has been archived by the owner on Jan 3, 2018. It is now read-only.

Decoding error with organizations endpoint #42

Closed
stout01 opened this issue May 24, 2017 · 7 comments
Closed

Decoding error with organizations endpoint #42

stout01 opened this issue May 24, 2017 · 7 comments

Comments

@stout01
Copy link

stout01 commented May 24, 2017

When the browser goes to decode the response from the organizations endpoint, there is a decoding error.

image

When trying to view the response in Fiddler, I receive this error:
image

The issue is resolved after I remove the compression middleware.

@robmcguinness
Copy link
Contributor

does this happen on other endpoints?

@stout01
Copy link
Author

stout01 commented May 24, 2017

I have not experienced this on any other endpoints

@KaseyPowers
Copy link
Contributor

Playing around with this error. I thought it might be something in my json so I removed chunks until it worked. I think it is triggered instead by json files larger than some arbitrary threshold.

@robmcguinness
Copy link
Contributor

Ekko uses Express and the compression middleware that has a threshold of 1k. i'm guessing the payloads with issue are the ones over 1k.

@robmcguinness
Copy link
Contributor

robmcguinness commented May 30, 2017

It appears this issue is not within availity-ekko but a bug in availity-workflow proxy contextRewrite setting. When ekko responds with json, workflow tries to rewrite the URL within the body response to match the host. During this process, workflow ends up corrupting the response body for gzipped contents. By default any payload over 1k is gzipped (under 1k is not gzipped).

@robmcguinness
Copy link
Contributor

@robmcguinness
Copy link
Contributor

Fixes in v2.1.1. Please npm install availity-workflow@latest --save

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants