Skip to content
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

Improve support to binary files #206

Closed
diego-aquino opened this issue Jun 3, 2024 · 0 comments · Fixed by #207
Closed

Improve support to binary files #206

diego-aquino opened this issue Jun 3, 2024 · 0 comments · Fixed by #207
Assignees
Milestone

Comments

@diego-aquino
Copy link
Member

No description provided.

@diego-aquino diego-aquino converted this from a draft issue Jun 3, 2024
@diego-aquino diego-aquino self-assigned this Jun 3, 2024
@diego-aquino diego-aquino added this to the v0.6.2 milestone Jun 3, 2024
@diego-aquino diego-aquino moved this from To do to In progress in Zimic Jun 3, 2024
@diego-aquino diego-aquino linked a pull request Jun 3, 2024 that will close this issue
diego-aquino added a commit that referenced this issue Jun 3, 2024
### Fixes
- [#zimic] Extended support to use binary files as response to
intercepted requests. Previously, the serialization algorithm for RPCs
between remote interceptors and interceptor servers could transfer
binary content incorrectly.
- [#zimic] Considered `application/xml` as plain text content.

### Tests
- [#zimic] Updated the body tests to use random bytes in binary file
contents, making sure that the data is processed correctly.

### Documentation
- [#zimic] Added a table showing how each content type is automatically
parsed by Zimic.
- [#zimic] Added a new section detailing request and response object of
intercepted resources.

Closes #206.
@github-project-automation github-project-automation bot moved this from In progress to Done in Zimic Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant