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.

Sign up for GitHub

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

Jump to bottom

Handling of HTTP Requests #395

Open
1 task
JohnNKing opened this issue Jun 19, 2023 · 1 comment
Open
1 task

Handling of HTTP Requests #395

JohnNKing opened this issue Jun 19, 2023 · 1 comment
Labels
devex/opex A development excellence or operational excellence backlog item.

Comments

@JohnNKing
Copy link
Contributor

DevEx/OpEx

How should the TI service handle non-HTTPS request?

Currently this results in a 301 permanent redirect. For an API client that may automatically follow redirects, is there any risk of data being sent unencrypted without the sending entity ever being aware? How does ReportStream's Waters API behave?

Alternative options may include:

  • Responding with an HTTP 400
  • Preventing socket connections to port 80

Tasks

  • Something.

Additional Context

Add any other context or screenshots about the work here.
@JohnNKing JohnNKing added the devex/opex A development excellence or operational excellence backlog item. label Jun 19, 2023
@JohnNKing JohnNKing mentioned this issue Jun 19, 2023
Merged
@pluckyswan
Copy link
Contributor

See thread for further context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
devex/opex A development excellence or operational excellence backlog item.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JohnNKing @pluckyswan