|
2018-05-07
| ||
| 17:07 | • Closed ticket [e72cf5e815]: Extended autoproxy to works with twapi for https (configurable) plus 3 other changes artifact: a0695a8190 user: aku | |
| 17:02 | Tkt [e72cf5e815] - Merged feature branch check-in: f14ecf1992 user: aku tags: trunk | |
|
2018-05-05
| ||
| 04:46 | • Ticket [e72cf5e815] Extended autoproxy to works with twapi for https (configurable) status still Open with 3 other changes artifact: 82d62d1578 user: apnadkarni | |
|
2018-05-01
| ||
| 18:07 | • Ticket [e72cf5e815]: 4 changes artifact: fe3dbe3ca8 user: aku | |
| 18:04 | • Ticket [e72cf5e815]: 3 changes artifact: 97303daf0a user: aku | |
| 17:58 | • Ticket [e72cf5e815]: 3 changes artifact: fb2ff2f943 user: aku | |
| 17:55 | • Ticket [e72cf5e815]: 3 changes artifact: 17f629fa06 user: aku | |
| 17:52 | • Ticket [e72cf5e815]: 3 changes artifact: d7bd8f3eef user: aku | |
| 17:45 | • Open ticket [e72cf5e815]. artifact: 7e08882aa7 user: aku | |
| 17:40 | http / autoproxy <EF> Ticket [e72cf5e815] Fixes before merge - Tweaked the documentation setup, placed the custom tls notes into the section instead of before it. - Using the in/ni operators means that the package and tests require Tcl 8.5+ Note, still seeing test failures on linux, where tests use twapi commands and are guarded only with have-tls. Still, tests are also described as using tls, so it is likely an issue in the package, not the test itself. This need some more investigation. check-in: e9af4d885f user: aku tags: autoproxy-twapi-support | |
|
2018-04-23
| ||
| 07:36 | • Ticket [e72cf5e815] Check if autoproxy could works with twapi for https status still Closed with 4 other changes artifact: 2875ae2a60 user: oehhar | |
|
2018-04-17
| ||
| 16:17 | • Closed ticket [e72cf5e815]. artifact: 6c64d48f2d user: oehhar | |
| 15:25 | Updated version info in pkgConfig.tcl and autoproxy.man. Ticket for this branch: [e72cf5e815] check-in: 0c15f14f78 user: oehhar tags: autoproxy-twapi-support | |
|
2017-11-10
| ||
| 14:08 | • New ticket [e72cf5e815] Check if autoproxy could works with twapi for https. artifact: 23572b2683 user: oehhar | |
| Ticket UUID: | e72cf5e815088248c923ed045372e4464f3e09a7 | |||
| Title: | Extended autoproxy to works with twapi for https (configurable) | |||
| Type: | RFE | Version: | trunk | |
| Submitter: | oehhar | Created on: | 2017-11-10 14:08:49 | |
| Subsystem: | http :: autoproxy | Assigned To: | aku | |
| Priority: | 8 | Severity: | Minor | |
| Status: | Closed | Last Modified: | 2018-05-07 17:07:34 | |
| Resolution: | Accepted | Closed By: | oehhar | |
| Closed on: | 2018-04-17 16:17:07 | |||
| Description: |
Twapi is helpful to be used for https on Windows instead the TLS package for update reasons (twapi gets updated with the operating system, with TLS (on windows), the program author must care to update openssl if required). For instance, it does not work with autoproxy. Wiki page for some details: http://wiki.tcl.tk/https It is examined in TWAPI and here, to find out:
Here is the twapi ticket: https://sourceforge.net/p/twapi/bugs/162/ | |||
| User Comments: |
aku added on 2018-05-07 17:07:34:
Integrated with trunk now. apnadkarni added on 2018-05-05 04:46:27: Tested on Win 10 with twapi with no failures. aku added on 2018-05-01 18:04:34: Fix pushed. Works for me now. Please retest in a twapi environment. aku added on 2018-05-01 17:58:31: I believe I know. The last test to make a successful configuration change is 1.2.4.1, setting tls_package to twapi. And for two, the `packageReset` procedure does not reset the new tls_package information. Thus it leaks to the 2.0.0 test. And as the 2.x tests do not configure the package for themselves they all think to use twapi. That works of course works in an environment which has twapi. Fixing now ... aku added on 2018-05-01 17:55:32: Pushed a fix for the multiple -setup clauses. This did not fix the linux test failures. Investigation continues aku added on 2018-05-01 17:52:15: I see no difference between the tests autoproxy 2.0.0 and 2.0.1, except the title and constraints. Setup, body, and cleanup are identical. Ditto for 2.1.0 and 2.1.1 I further see multiple -setup declarations in these tests. I do not believe that both will be run, only the second. I wonder if that may be the issue, i.e. packageReset missing. aku added on 2018-05-01 17:45:11: Re-opened. Still to merge. Currently investigating Linux testsuite failures. Notes: - Tweaked the doc setup to have the custom tls note part of the second, and not before - Added Tcl 8.5 requirement to have `in`/`ni` operators. oehhar added on 2018-04-23 07:36:22: For the records, the patch was tested with success by Harald and Alexandru (see the clt thread). Thus I favor to merge it. Thank you, Harald oehhar added on 2018-04-17 16:17:07: Fixed by Ashok in branch "autoproxy-twapi-support". Thank you, ticket closed, Harald | |||