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

Add (experimental) API proxy to Kalamar #91

Closed
Akron opened this issue Jul 4, 2019 · 1 comment
Closed

Add (experimental) API proxy to Kalamar #91

Akron opened this issue Jul 4, 2019 · 1 comment
Assignees

Comments

@Akron
Copy link
Member

Akron commented Jul 4, 2019

Mojolicious now provides a low cost proxy handler, that should be tested as the primary entrance for API request. This has the following advantages over Apache proxying:

  • consistent client IP handling
  • consistent Piwik integration
  • consistent API requests (removal of current API proxies like matchinfo)
  • single open port for Vagrant
@Akron
Copy link
Member Author

Akron commented Jul 5, 2019

I added a working proxy we should test before deployment. As long as /api is governed by Apache, the changes shouldn't have any effect in deployment, but we should make sure, the API exposure is no security problem. If we want to limit the proxy to certain APIs first, we should do that.

The proxy will be handled as experimental as long as the method in Mojolicious is considered experimental.

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

No branches or pull requests

3 participants