[GitHub] trafficserver pull request #644: [TS 4437] Add new limit rate example plugin

Github user yatsukhnenko closed the pull request at: https://github.com/apache/trafficserver/pull/644 --- 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

[GitHub] trafficserver pull request #806: TS-4304: implementation of ConditionUrl::ap...

Github user yatsukhnenko closed the pull request at: https://github.com/apache/trafficserver/pull/806 --- 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

[GitHub] trafficserver issue #806: TS-4304: implementation of ConditionUrl::append_va...

Github user yatsukhnenko commented on the issue: https://github.com/apache/trafficserver/pull/806 @zwoop, did you look at this? What's wrong? --- 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] trafficserver issue #806: TS-4304: implementation of ConditionUrl::append_va...

Github user yatsukhnenko commented on the issue: https://github.com/apache/trafficserver/pull/806 @zwoop, I added the same features as in eval method --- 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

[GitHub] trafficserver issue #815: TS-4680: thread safe initialization in TS*DirGet()...

Github user yatsukhnenko commented on the issue: https://github.com/apache/trafficserver/pull/815 @zwoop, @jpeach, something like 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

[GitHub] trafficserver issue #644: [TS 4437] Add new limit rate example plugin

Github user yatsukhnenko commented on the issue: https://github.com/apache/trafficserver/pull/644 @zwoop, I did squashing and fixing clang-format and spelling typos. Review please :) --- If your project is set up for it, you can reply to this email and have your reply appear

[GitHub] trafficserver pull request #815: TS-4680: thread safe initialization in TS*D...

GitHub user yatsukhnenko opened a pull request: https://github.com/apache/trafficserver/pull/815 TS-4680: thread safe initialization in TS*DirGet() functions @zwoop, @jpeach, review please. I'm not sure about that. You can merge this pull request into a Git repository by running

[GitHub] trafficserver issue #805: TS-4595: TSRuntimeDirGet

Github user yatsukhnenko commented on the issue: https://github.com/apache/trafficserver/pull/805 @zwoop, I chaneged `Synopsis` and `Description` sections --- 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

[GitHub] trafficserver issue #805: TS-4595: TSRuntimeDirGet

Github user yatsukhnenko commented on the issue: https://github.com/apache/trafficserver/pull/805 [TS-4680](https://issues.apache.org/jira/browse/TS-4680) --- 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

[jira] [Created] (TS-4680) Not thread safe initialization in TS*DirGet() functions

Pavlo Yatsukhnenko created TS-4680: -- Summary: Not thread safe initialization in TS*DirGet() functions Key: TS-4680 URL: https://issues.apache.org/jira/browse/TS-4680 Project: Traffic Server

[GitHub] trafficserver issue #804: TS-4624: use the server UUID in the Via header

Github user yatsukhnenko commented on the issue: https://github.com/apache/trafficserver/pull/804 [This](https://issues.apache.org/jira/browse/TS-2819) one? --- 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

[GitHub] trafficserver issue #805: TS-4595: TSRuntimeDirGet

Github user yatsukhnenko commented on the issue: https://github.com/apache/trafficserver/pull/805 I'll try to fix it a bit letter if it's not urgent --- 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

[GitHub] trafficserver issue #804: TS-4624: use the server UUID in the Via header

Github user yatsukhnenko commented on the issue: https://github.com/apache/trafficserver/pull/804 > What do you think of a future feature (config) to disable this Via checking completely? If I know there's not chance of a loop, why bother checking the Via header? @zw

[GitHub] trafficserver pull request #804: TS-4624: use the server UUID in the Via hea...

Github user yatsukhnenko commented on a diff in the pull request: https://github.com/apache/trafficserver/pull/804#discussion_r71085622 --- Diff: proxy/http/HttpTransactHeaders.cc --- @@ -750,12 +752,10 @@ HttpTransactHeaders::insert_via_header_in_request(HttpTransact::State *s

[GitHub] trafficserver issue #804: TS-4624: use the server UUID in the Via header

Github user yatsukhnenko commented on the issue: https://github.com/apache/trafficserver/pull/804 Thanks for explaining about API usage --- 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] trafficserver pull request #804: TS-4624: use the server UUID in the Via hea...

Github user yatsukhnenko commented on a diff in the pull request: https://github.com/apache/trafficserver/pull/804#discussion_r71084817 --- Diff: proxy/http/HttpTransactHeaders.cc --- @@ -750,12 +752,10 @@ HttpTransactHeaders::insert_via_header_in_request(HttpTransact::State *s

[GitHub] trafficserver issue #805: TS-4595: TSRuntimeDirGet

Github user yatsukhnenko commented on the issue: https://github.com/apache/trafficserver/pull/805 I added tests and created empty doc file(writing documentation is not a good idia considering my English level :shame:) --- If your project is set up for it, you can reply to this email

[GitHub] trafficserver issue #804: TS-4624: use the server UUID in the Via header

Github user yatsukhnenko commented on the issue: https://github.com/apache/trafficserver/pull/804 Don't quite understand why public API can't be used in internal code, but ok, changed code to `Machine::instance()->uuid.getString()` --- If your project is set up for it, you can re

[GitHub] trafficserver pull request #806: TS-4304: implementation of ConditionUrl::ap...

GitHub user yatsukhnenko opened a pull request: https://github.com/apache/trafficserver/pull/806 TS-4304: implementation of ConditionUrl::append_value You can merge this pull request into a Git repository by running: $ git pull https://github.com/yatsukhnenko/trafficserver TS

[GitHub] trafficserver pull request #805: TS-4595: TSRuntimeDirGet

GitHub user yatsukhnenko opened a pull request: https://github.com/apache/trafficserver/pull/805 TS-4595: TSRuntimeDirGet You can merge this pull request into a Git repository by running: $ git pull https://github.com/yatsukhnenko/trafficserver TS-4595 Alternatively you can

[GitHub] trafficserver pull request #804: TS-4624: use the server UUID in the Via hea...

GitHub user yatsukhnenko opened a pull request: https://github.com/apache/trafficserver/pull/804 TS-4624: use the server UUID in the Via header If I correctly understood the task :smiley: You can merge this pull request into a Git repository by running: $ git pull https

[GitHub] trafficserver issue #644: [TS 4437] Add new limit rate example plugin

Github user yatsukhnenko commented on the issue: https://github.com/apache/trafficserver/pull/644 It does what it should. If somebody will help to solve the problem with multiple writing to cache this will fine open source example :-) --- If your project is set up for it, you can

[GitHub] trafficserver issue #644: [TS 4437] Add new limit rate example plugin

Github user yatsukhnenko commented on the issue: https://github.com/apache/trafficserver/pull/644 Closing PR is the only way to attract your attention :smile: If serious, I think you shouldn't land this as is (even after squashing and fixing spelling typos) because it sometimes

[GitHub] trafficserver pull request #644: [TS 4437] Add new limit rate example plugin

GitHub user yatsukhnenko reopened a pull request: https://github.com/apache/trafficserver/pull/644 [TS 4437] Add new limit rate example plugin You can merge this pull request into a Git repository by running: $ git pull https://github.com/yatsukhnenko/trafficserver TS-4437

[GitHub] trafficserver pull request #644: [TS 4437] Add new limit rate example plugin

Github user yatsukhnenko closed the pull request at: https://github.com/apache/trafficserver/pull/644 --- 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

[GitHub] trafficserver issue #644: [TS 4437] Add new limit rate example plugin

Github user yatsukhnenko commented on the issue: https://github.com/apache/trafficserver/pull/644 @zwoop, did you review the code? Is it absolutely wrong and I should throw it out and close this PR? can you give any feedback? --- If your project is set up for it, you can reply

[jira] [Closed] (TS-4488) Segmentation fault at HttpSM::tunnel_handler_ua

[ https://issues.apache.org/jira/browse/TS-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavlo Yatsukhnenko closed TS-4488. -- > Segmentation fault at HttpSM::tunnel_handler

[jira] [Updated] (TS-4488) Segmentation fault at HttpSM::tunnel_handler_ua

[ https://issues.apache.org/jira/browse/TS-4488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavlo Yatsukhnenko updated TS-4488: --- Flags: Patch Description: From Github PR #674 Summary: Segmentation fault

[jira] [Created] (TS-4488) Segmentation fault

Pavlo Yatsukhnenko created TS-4488: -- Summary: Segmentation fault Key: TS-4488 URL: https://issues.apache.org/jira/browse/TS-4488 Project: Traffic Server Issue Type: Bug Reporter

[jira] [Created] (TS-4443) regex_remap: fix $i substitution

Pavlo Yatsukhnenko created TS-4443: -- Summary: regex_remap: fix $i substitution Key: TS-4443 URL: https://issues.apache.org/jira/browse/TS-4443 Project: Traffic Server Issue Type