Skip to content
This repository has been archived by the owner on Feb 22, 2023. It is now read-only.

Ensure proxy can work for all content types #393

Closed
jkelvie opened this issue Oct 5, 2017 · 4 comments
Closed

Ensure proxy can work for all content types #393

jkelvie opened this issue Oct 5, 2017 · 4 comments
Assignees
Milestone

Comments

@jkelvie
Copy link
Member

jkelvie commented Oct 5, 2017

Not just JSON. It should also allow for:

  • Images
  • Javascript
  • HTML
  • CSS

Essentially, we want to test and ensure that it is working perfectly for proxying a web server with general content.

In cases where logging is enabled via the proxy, it should only still capture JSON though.

@jkelvie jkelvie changed the title Ensure proxy can work for call content types Ensure proxy can work for all content types Oct 5, 2017
@jkelvie jkelvie added this to the BST 1.1 milestone Oct 6, 2017
@jkelvie
Copy link
Member Author

jkelvie commented Oct 20, 2017

Need to make sure it works with redirects as well

@jperata
Copy link
Contributor

jperata commented Nov 8, 2017

Redirect work needs update for http-buffer to assure response is forwarded directly

@jperata
Copy link
Contributor

jperata commented Jan 3, 2018

Currently we have some issues with images, reviewing last standing changes. And moving to current Sprint of work

@jperata
Copy link
Contributor

jperata commented Jan 3, 2018

Estimated Remaining Time, 2 days

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

2 participants