Github user asfgit commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/incubator-trafficcontrol-PR-trafficops-test/24/
---
If your
Github user asfgit commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user dewrich commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
Carried forward from slack for reference:
Password format changed from SHA1 to scrypt.
http://search.cpan.org/~mik/Crypt-ScryptKDF-0.006/lib/Crypt/ScryptKDF.pm
Github user dewrich commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
@amiryesh I think I discovered another issue. When you send the Mojo
cookie now, it flows through to Traffic Ops accordingly, but should we also
need the "capabilities" guard
Github user dewrich commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
@amiryesh Another useful piece of information would be timings. For
example: "How long did it take to call that backend, in milliseconds?"
---
If your project is set up for it,
Github user dewrich commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
Another something to play with: https://github.com/elazarl/goproxy
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user dewrich commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
@amiryesh Another feature request
Out of curiousity, I configured the gateway to "front" Traffic Ops entirely
(and it worked!), but I had to reconfigure the "/login" (which
Github user dewrich commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
@amiryesh Another request, please make the server.key, etc configurable,
ops may want to put them in a different location than the current directory.
---
If your project is set up
Github user dewrich commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
Just a thought, it might be useful to expose a route on the webfront that
lists the "backend" routes it's mapping (in .json form). This way, I can
remotely ask the gateway about
Github user dewrich commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
Re: grouping auth and webfront into a single directory. Maybe this is the
start of a Dev list discussion about how to structure our Microservices, where
webfront and auth are
Github user dewrich commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
@amiryesh Nevermind about the 502 bad gateway. I can't seem to reproduce
it now if I find it again, I'll let you know.
---
If your project is set up for it, you can reply to this
Github user amiryesh commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
@dewrich Hi, Thanks for your comments.
Regarding better error handling, I my tests I do get a 502 response in this
case.
Can you share your setup details to help me
Github user amiryesh commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
@limited Right
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user limited commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
Thanks Amir-
Perfect sense! Just to make sure I understood correctly, we will keep
both the auth server and API gateway as optional components that could be
switched out
Github user amiryesh commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
@limited Hi, I agree with your view on the benefits of using industry
standard software wherever applicable. Let me share my view on how the API GW
and the auth server are to be
Github user dewrich commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
Suggestions:
1. Documentation:
Once I understood how the pieces fit together, it was relatively simple
(but I also had some background about how it was built). This
Github user dewrich commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
FYI: I was able to access a TO API endpoint from the webfront with success.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user dewrich commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
@amiryesh Thanks for clarification. It wasn't obvious that the "auth" dir
and "webfront" was included in the "apigateway"
---
If your project is set up for it, you can reply to
Github user limited commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
This look pretty nice Amir-
Have you considered using an open source proxy like nginx or varnish in
place of writing our own? Both pieces of software can almost certainly
Github user amiryesh commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
Hi, glad to hear you are taking the effort of using the GW.
Did you get to see webfront/README.md or auth/README.md?
The auth server is responsible for login. The auth
Github user ryandurfey commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
Working to get a committer to evaluate.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user rob05c commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
Looks good to me (once its rebased).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user mitchell852 commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/567
@amiryesh - can you rebase this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
23 matches
Mail list logo
