Dan Kirkwood created TC-400:
---
Summary: incomplete error message from TO api
Key: TC-400
URL: https://issues.apache.org/jira/browse/TC-400
Project: Traffic Control
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/TC-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Kirkwood closed TC-399.
---
Resolution: Not A Bug
this is not an issue -- PUT expects to have all data provided for the object..
> PUT /api/1
[
https://issues.apache.org/jira/browse/TC-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056589#comment-16056589
]
Dan Kirkwood commented on TC-399:
-
this is not an issue -- PUT expects to have all data provid
GitHub user serDrem opened a pull request:
https://github.com/apache/incubator-trafficcontrol/pull/695
TrafficMonitor IPV6 improvements
Enables TM to poll health information over IPV6, and optionally combine it
with IPV4 information for traffic router.
You can merge this pull reque
Github user serDrem closed the pull request at:
https://github.com/apache/incubator-trafficcontrol/pull/694
---
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 and wishes so, or if
GitHub user serDrem opened a pull request:
https://github.com/apache/incubator-trafficcontrol/pull/694
TrafficMonitor IPV6 improvements
Enables TM to poll health information over IPV6, and optionally combine it
with IPV4 information for traffic router.
You can merge this pull reque
Github user serDrem closed the pull request at:
https://github.com/apache/incubator-trafficcontrol/pull/693
---
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 and wishes so, or if
[
https://issues.apache.org/jira/browse/TC-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Kirkwood resolved TC-260.
-
Resolution: Fixed
> TO crash on missing regex on creating delivery service in UI
> ---
Dan Kirkwood created TC-399:
---
Summary: PUT /api/1.2/deliveryservices/:serverId: overwrites some
data with null/empty
Key: TC-399
URL: https://issues.apache.org/jira/browse/TC-399
Project: Traffic Control
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 an
GitHub user serDrem opened a pull request:
https://github.com/apache/incubator-trafficcontrol/pull/693
TrafficMonitor IPV6 improvements
Enables TM to poll health information over IPV6, and optionally combine it
with IPV4 information for traffic router.
You can merge this pull requ
[
https://issues.apache.org/jira/browse/TC-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Kirkwood resolved TC-395.
-
Resolution: Fixed
> traffic_ops install doc references rpm on apache build server
> --
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 for
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 co
Github user dewrich commented on a diff in the pull request:
https://github.com/apache/incubator-trafficcontrol/pull/567#discussion_r123063580
--- Diff: traffic_ops/experimental/webfront/webfront.go ---
@@ -122,188 +145,324 @@ func main() {
Logger.Fatal(http.ListenAndServeT
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-trafficcontrol/pull/692
---
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 and wishes so, or if t
GitHub user dg4prez opened a pull request:
https://github.com/apache/incubator-trafficcontrol/pull/692
fix commenting problem
Fixes problems in the seeds and patches sql files that prevent upgrades
from running.
You can merge this pull request into a Git repository by running:
[
https://issues.apache.org/jira/browse/TC-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056252#comment-16056252
]
ASF GitHub Bot commented on TC-398:
---
GitHub user nir-sopher opened a pull request:
http
GitHub user nir-sopher opened a pull request:
https://github.com/apache/incubator-trafficcontrol/pull/691
[TC-398] "create user" API - moving password hashing to scrypt
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nir-sopher/i
Nir Sopher created TC-398:
-
Summary: Create User API - Broken due to merge issue
Key: TC-398
URL: https://issues.apache.org/jira/browse/TC-398
Project: Traffic Control
Issue Type: Bug
Compo
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 can
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-trafficcontrol/pull/628
---
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 and wishes so, or if t
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 as
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 th
Github user jrushford commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/628
@dg4prez and @dneuman64 - I've fixed this pr to include the ui code,
squashed and rebased.
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-trafficcontrol/pull/561
---
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 and wishes so, or if t
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-trafficcontrol/pull/662
---
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 and wishes so, or if t
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-trafficcontrol/pull/670
---
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 and wishes so, or if t
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 valid
29 matches
Mail list logo
