date:20140313


[ 
https://issues.apache.org/jira/browse/TS-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933370#comment-13933370
 ] 

Leif Hedstrom commented on TS-2634:
---

[~jpe...@apache.org] Well, it looks like all other platforms have the default 
at --no-as-needed, whereas Ubuntu 13.10 has --as-needed. It's odd to me though 
that libtsutil.so claims to have a libhwloc.so dependency (according to ldd), 
yet, linking with just -ltsutils does not work without another explicit 
-lhwloc...

Note that adding -Wl,--no-as-needed is tricky, in that it has to come early on 
in the link line. I tried various combinations in the Makefile.am syntax, but 
none worked.

I'm not sure what the execution would fail with @hwloc_libs@ in 
traffic_manager, let me test that.

 Build broken on Ubuntu Saucy
 

 Key: TS-2634
 URL: https://issues.apache.org/jira/browse/TS-2634
 Project: Traffic Server
  Issue Type: Bug
Reporter: Phil Sorber
Assignee: Leif Hedstrom

 libhwloc not linked properly on ubuntu 13.10:
 /usr/bin/ld: ../lib/ts/.libs/libtsutil.so: undefined reference to symbol 
 'hwloc_get_type_depth'
 /usr/lib/x86_64-linux-gnu/libhwloc.so: error adding symbols: DSO missing from 
 command line



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (TS-2635) remove unused include net/ppp_defs.h


 [ 
https://issues.apache.org/jira/browse/TS-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-2635:
--

Assignee: Igor Galić

 remove unused include net/ppp_defs.h
 --

 Key: TS-2635
 URL: https://issues.apache.org/jira/browse/TS-2635
 Project: Traffic Server
  Issue Type: Bug
Reporter: Igor Galić
Assignee: Igor Galić
 Fix For: 5.0.0


 we include {{net/ppp_defs.h}} but it is never used.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (TS-2605) delete unused code


 [ 
https://issues.apache.org/jira/browse/TS-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-2605:
--

Assignee: Phil Sorber  (was: Leif Hedstrom)

 delete unused code
 --

 Key: TS-2605
 URL: https://issues.apache.org/jira/browse/TS-2605
 Project: Traffic Server
  Issue Type: Improvement
  Components: Core, TProxy
Reporter: sherlockhua
Assignee: Phil Sorber
  Labels: review
 Fix For: 5.0.0

 Attachments: 0001-TS-2605-delete-unused-code-from-proxy-Main.cc.patch


 I'm newer to the traffic server project, when I read the source code, I found 
 this code snippets have not used. in proxy/Main.cc, 1350 line. the code 
 sippnets is like follow:
 1347   // This call is required for win_9xMe
 1348   //without this this_ethread() is failing when
 1349   //start_HttpProxyServer is called from main thread
 1350   Thread *main_thread = NEW(new EThread);
   
 
 1351   main_thread-set_specific();
 but I found when  eventProcessor.start(num_of_net_threads, stacksize) is 
 execute, in function start of  eventProcessor will overwrite the thread 
 specific data which set above, here is the code snippets:
 130 EventProcessor::start(int n_event_threads, size_t stacksize)
 131 {
 132   char thr_name[MAX_THREAD_NAME_LENGTH];
 133   int i;
 134 
 135   // do some sanity checking.
 136   static int started = 0;
 137   ink_release_assert(!started);
 138   ink_release_assert(n_event_threads  0  n_event_threads = 
 MAX_EVENT_THREADS);
 139   started = 1;
 140 
 141   n_ethreads = n_event_threads;
 142   n_thread_groups = 1;
 143 
 144   int first_thread = 1;
 145 
 146   for (i = 0; i  n_event_threads; i++) {
 147 EThread *t = NEW(new EThread(REGULAR, i));
 148 if (first_thread  !i) {
 149   ink_thread_setspecific(Thread::thread_data_key, t); //overwrite
 150   global_mutex = t-mutex;
 151   t-cur_time = ink_get_based_hrtime_internal();
 152 }
 153 all_ethreads[i] = t;
 154 
 155 eventthread[ET_CALL][i] = t;
 156 t-set_event_type((EventType) ET_CALL);
 157   }
 so I think the main_thread should discarded, and make code more clear to 
 read, thank you. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (TS-2632) Range request will always lock object in cache, even thought it's rarely cacheable

2014-03-13 Thread Alan M. Carroll (JIRA)

[
https://issues.apache.org/jira/browse/TS-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933438#comment-13933438
]

Alan M. Carroll commented on TS-2632:
-

I think overall this is a good change - it seems very unlikely that any modern
server will return a full object in response to a range request. I will note,
however, that for someone to support this, all you have to do is to remove the
Range: header on the request as you wouldn't know until after sending the
request if this would happen.

Range request will always lock object in cache, even thought it's rarely
cacheable
--

Key: TS-2632
URL: https://issues.apache.org/jira/browse/TS-2632
Project: Traffic Server
Issue Type: Bug
Components: Cache, HTTP
Reporter: Leif Hedstrom
Assignee: Leif Hedstrom
Fix For: 5.0.0

Right now, if a client sends a Range: request, we still lock the URL in the
cache, under the assumption that it will be written to. Since we don't
support partial objects, in almost all cases, we'll not write the object and
therefore release the object.
I suggest we change this such that we never try to write lock a URL in the
presence of a Range: header in the client request. This will allow other
requests to go to origin faster, and better yet, it allows a request without
a Range: header to properly lock the URL for writing. This turns out to be
important for implementing e.g. background filling as a plugin.
There is one use case where this might be useful; If the origin does not
respond with a 206 (partial object), we can now cache the full object.
However, this is a pretty rare case, and for someone to support this, all you
have to do is to remove the Range: header on the request.
I'm opening up this bug right now for discussion, if anyone have any concerns
about this change, please let me know. It is an incompatible change,
without configuration options, but that should be ok for the v5.0.0 release.

--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (TS-2634) Build broken on Ubuntu Saucy


[ 
https://issues.apache.org/jira/browse/TS-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933453#comment-13933453
 ] 

James Peach commented on TS-2634:
-

The link ordering problem is well know to google. When I looked at this a while 
ago, people were having lots of trouble getting lib tool to use {{--as-needed}} 
because of the way it reorders its options.

As for recursive linking; that's a standard unix-ism. OS X does the right thing 
(IMHO), but Linux has always required that the top level command link the full 
set of dependencies, which is why things like pkg-config are needed.

 Build broken on Ubuntu Saucy
 

 Key: TS-2634
 URL: https://issues.apache.org/jira/browse/TS-2634
 Project: Traffic Server
  Issue Type: Bug
Reporter: Phil Sorber
Assignee: Leif Hedstrom

 libhwloc not linked properly on ubuntu 13.10:
 /usr/bin/ld: ../lib/ts/.libs/libtsutil.so: undefined reference to symbol 
 'hwloc_get_type_depth'
 /usr/lib/x86_64-linux-gnu/libhwloc.so: error adding symbols: DSO missing from 
 command line



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (TS-2634) Build broken on Ubuntu Saucy


 [ 
https://issues.apache.org/jira/browse/TS-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Leif Hedstrom updated TS-2634:
--

Assignee: Phil Sorber  (was: Leif Hedstrom)

 Build broken on Ubuntu Saucy
 

 Key: TS-2634
 URL: https://issues.apache.org/jira/browse/TS-2634
 Project: Traffic Server
  Issue Type: Bug
Reporter: Phil Sorber
Assignee: Phil Sorber

 libhwloc not linked properly on ubuntu 13.10:
 /usr/bin/ld: ../lib/ts/.libs/libtsutil.so: undefined reference to symbol 
 'hwloc_get_type_depth'
 /usr/lib/x86_64-linux-gnu/libhwloc.so: error adding symbols: DSO missing from 
 command line



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (TS-2626) Problem with TS-312 - Always share Keep Alive


 [ 
https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tommy Lee updated TS-2626:
--

Summary: Problem with TS-312 - Always share Keep Alive  (was: Problem with 
Referer Header ( Forward Mode ))

 Problem with TS-312 - Always share Keep Alive
 -

 Key: TS-2626
 URL: https://issues.apache.org/jira/browse/TS-2626
 Project: Traffic Server
  Issue Type: Bug
  Components: HTTP
Reporter: Tommy Lee
 Fix For: 5.0.0

 Attachments: tcpdump.txt


 We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some 
 websites that uses Authorization Header.
 We always get 401 ( Unauthorized ) response.
 I'm attaching two debug files. One with ATS-3.2.2 that's working and one with 
 ATS-5.0.0 that's broken.
 Almost the same records.config for both tests.
 I'm looking for changes in source code too. I'll update the issue if I find 
 an answer.
 To devs: Could the question mark after the exchange  can cause that ? This 
 is the only modification between these two versions.
 ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange?
 ATS-5.0.0 GET -  GET http://webmail.candidomendes.edu.br/exchange
 Thanks.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (TS-2626) Problem with TS-312 - Always share Keep Alive


[ 
https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933502#comment-13933502
 ] 

Tommy Lee commented on TS-2626:
---

After extensive tests between patches we have found the problem.

I don't know why, but changes for TS-312 affect this type of connection.

After revert, everything is OK.

Brian, if you need more tests please let me know.

Thanks.
 


 Problem with TS-312 - Always share Keep Alive
 -

 Key: TS-2626
 URL: https://issues.apache.org/jira/browse/TS-2626
 Project: Traffic Server
  Issue Type: Bug
  Components: HTTP
Reporter: Tommy Lee
 Fix For: 5.0.0

 Attachments: tcpdump.txt


 We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some 
 websites that uses Authorization Header.
 We always get 401 ( Unauthorized ) response.
 I'm attaching two debug files. One with ATS-3.2.2 that's working and one with 
 ATS-5.0.0 that's broken.
 Almost the same records.config for both tests.
 I'm looking for changes in source code too. I'll update the issue if I find 
 an answer.
 To devs: Could the question mark after the exchange  can cause that ? This 
 is the only modification between these two versions.
 ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange?
 ATS-5.0.0 GET -  GET http://webmail.candidomendes.edu.br/exchange
 Thanks.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Comment Edited] (TS-2626) Problem with TS-312 - Always share Keep Alive


[ 
https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933502#comment-13933502
 ] 

Tommy Lee edited comment on TS-2626 at 3/13/14 4:49 PM:


After extensive tests between patches we have found the problem.

I don't know why, but changes for TS-312 affect this type of connection.

After revert, everything is OK.

Brian, if you need more tests please let me know.

James, thanks for you attention and help.

Thanks.
 



was (Author: tommylee):
After extensive tests between patches we have found the problem.

I don't know why, but changes for TS-312 affect this type of connection.

After revert, everything is OK.

Brian, if you need more tests please let me know.

Thanks.
 


 Problem with TS-312 - Always share Keep Alive
 -

 Key: TS-2626
 URL: https://issues.apache.org/jira/browse/TS-2626
 Project: Traffic Server
  Issue Type: Bug
  Components: HTTP
Reporter: Tommy Lee
 Fix For: 5.0.0

 Attachments: tcpdump.txt


 We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some 
 websites that uses Authorization Header.
 We always get 401 ( Unauthorized ) response.
 I'm attaching two debug files. One with ATS-3.2.2 that's working and one with 
 ATS-5.0.0 that's broken.
 Almost the same records.config for both tests.
 I'm looking for changes in source code too. I'll update the issue if I find 
 an answer.
 To devs: Could the question mark after the exchange  can cause that ? This 
 is the only modification between these two versions.
 ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange?
 ATS-5.0.0 GET -  GET http://webmail.candidomendes.edu.br/exchange
 Thanks.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (TS-2626) Problem with TS-312 - Always share Keep Alive


[ 
https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933522#comment-13933522
 ] 

James Peach commented on TS-2626:
-

Does setting {{proxy.config.http.attach_server_session_to_client}} to 1 help?

 Problem with TS-312 - Always share Keep Alive
 -

 Key: TS-2626
 URL: https://issues.apache.org/jira/browse/TS-2626
 Project: Traffic Server
  Issue Type: Bug
  Components: HTTP
Reporter: Tommy Lee
 Fix For: 5.0.0

 Attachments: tcpdump.txt


 We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some 
 websites that uses Authorization Header.
 We always get 401 ( Unauthorized ) response.
 I'm attaching two debug files. One with ATS-3.2.2 that's working and one with 
 ATS-5.0.0 that's broken.
 Almost the same records.config for both tests.
 I'm looking for changes in source code too. I'll update the issue if I find 
 an answer.
 To devs: Could the question mark after the exchange  can cause that ? This 
 is the only modification between these two versions.
 ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange?
 ATS-5.0.0 GET -  GET http://webmail.candidomendes.edu.br/exchange
 Thanks.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (TS-2636) Enhance ATS custom logging to support WIPE filter action

2014-03-13 Thread Sudheer Vinukonda (JIRA)

Sudheer Vinukonda created TS-2636:
-

 Summary: Enhance ATS custom logging to support WIPE filter action
 Key: TS-2636
 URL: https://issues.apache.org/jira/browse/TS-2636
 Project: Traffic Server
  Issue Type: New Feature
  Components: Logging
Reporter: Sudheer Vinukonda


Currently, ATS custom logging supports LogFilters with actions Accept, Reject. 
This feature request is to add a new filter action WIPE. WIPE can be used in 
hiding sensitive parameters (e.g. userid, password) within the query part of a 
URL. Attached is a draft version of the patch. Kindly review and comment. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (TS-2626) Problem with TS-312 - Always share Keep Alive


[ 
https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933540#comment-13933540
 ] 

Tommy Lee commented on TS-2626:
---

James,

 GIT version with CONFIG proxy.config.http.attach_server_session_to_client INT 
1 works.
 

 Problem with TS-312 - Always share Keep Alive
 -

 Key: TS-2626
 URL: https://issues.apache.org/jira/browse/TS-2626
 Project: Traffic Server
  Issue Type: Bug
  Components: HTTP
Reporter: Tommy Lee
 Fix For: 5.0.0

 Attachments: tcpdump.txt


 We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some 
 websites that uses Authorization Header.
 We always get 401 ( Unauthorized ) response.
 I'm attaching two debug files. One with ATS-3.2.2 that's working and one with 
 ATS-5.0.0 that's broken.
 Almost the same records.config for both tests.
 I'm looking for changes in source code too. I'll update the issue if I find 
 an answer.
 To devs: Could the question mark after the exchange  can cause that ? This 
 is the only modification between these two versions.
 ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange?
 ATS-5.0.0 GET -  GET http://webmail.candidomendes.edu.br/exchange
 Thanks.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (TS-2636) Enhance ATS custom logging to support WIPE filter action

2014-03-13 Thread Sudheer Vinukonda (JIRA)


 [ 
https://issues.apache.org/jira/browse/TS-2636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sudheer Vinukonda updated TS-2636:
--

Attachment: ts2636.diff

 Enhance ATS custom logging to support WIPE filter action
 

 Key: TS-2636
 URL: https://issues.apache.org/jira/browse/TS-2636
 Project: Traffic Server
  Issue Type: New Feature
  Components: Logging
Reporter: Sudheer Vinukonda
 Attachments: ts2636.diff


 Currently, ATS custom logging supports LogFilters with actions Accept, 
 Reject. This feature request is to add a new filter action WIPE. WIPE can 
 be used in hiding sensitive parameters (e.g. userid, password) within the 
 query part of a URL. Attached is a draft version of the patch. Kindly review 
 and comment. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (TS-2637) traffic_line option to list statistics

James Peach created TS-2637:
---

 Summary: traffic_line option to list statistics
 Key: TS-2637
 URL: https://issues.apache.org/jira/browse/TS-2637
 Project: Traffic Server
  Issue Type: New Feature
  Components: Management, Management API
Reporter: James Peach


It's hard to find configuration options and statistics because the 
documentation often lags. We should have a way for users to list records and 
find out what is available.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (TS-2637) traffic_line option to list statistics


 [ 
https://issues.apache.org/jira/browse/TS-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Peach updated TS-2637:


Fix Version/s: 5.0.0
 Assignee: James Peach

 traffic_line option to list statistics
 --

 Key: TS-2637
 URL: https://issues.apache.org/jira/browse/TS-2637
 Project: Traffic Server
  Issue Type: New Feature
  Components: Management, Management API
Reporter: James Peach
Assignee: James Peach
 Fix For: 5.0.0


 It's hard to find configuration options and statistics because the 
 documentation often lags. We should have a way for users to list records and 
 find out what is available.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (TS-2626) Problem with TS-312 - Always share Keep Alive


[ 
https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933548#comment-13933548
 ] 

James Peach commented on TS-2626:
-

Is this NTLM authorization?

 Problem with TS-312 - Always share Keep Alive
 -

 Key: TS-2626
 URL: https://issues.apache.org/jira/browse/TS-2626
 Project: Traffic Server
  Issue Type: Bug
  Components: HTTP
Reporter: Tommy Lee
 Fix For: 5.0.0

 Attachments: tcpdump.txt


 We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some 
 websites that uses Authorization Header.
 We always get 401 ( Unauthorized ) response.
 I'm attaching two debug files. One with ATS-3.2.2 that's working and one with 
 ATS-5.0.0 that's broken.
 Almost the same records.config for both tests.
 I'm looking for changes in source code too. I'll update the issue if I find 
 an answer.
 To devs: Could the question mark after the exchange  can cause that ? This 
 is the only modification between these two versions.
 ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange?
 ATS-5.0.0 GET -  GET http://webmail.candidomendes.edu.br/exchange
 Thanks.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (TS-2626) Problem with TS-312 - Always share Keep Alive


[ 
https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933554#comment-13933554
 ] 

Tommy Lee commented on TS-2626:
---

Yep.

 Problem with TS-312 - Always share Keep Alive
 -

 Key: TS-2626
 URL: https://issues.apache.org/jira/browse/TS-2626
 Project: Traffic Server
  Issue Type: Bug
  Components: HTTP
Reporter: Tommy Lee
 Fix For: 5.0.0

 Attachments: tcpdump.txt


 We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some 
 websites that uses Authorization Header.
 We always get 401 ( Unauthorized ) response.
 I'm attaching two debug files. One with ATS-3.2.2 that's working and one with 
 ATS-5.0.0 that's broken.
 Almost the same records.config for both tests.
 I'm looking for changes in source code too. I'll update the issue if I find 
 an answer.
 To devs: Could the question mark after the exchange  can cause that ? This 
 is the only modification between these two versions.
 ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange?
 ATS-5.0.0 GET -  GET http://webmail.candidomendes.edu.br/exchange
 Thanks.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (TS-2626) Problem with TS-312 - Always share Keep Alive + NTLM Authorization


 [ 
https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tommy Lee updated TS-2626:
--

Summary: Problem with TS-312 - Always share Keep Alive + NTLM Authorization 
 (was: Problem with TS-312 - Always share Keep Alive)

 Problem with TS-312 - Always share Keep Alive + NTLM Authorization
 --

 Key: TS-2626
 URL: https://issues.apache.org/jira/browse/TS-2626
 Project: Traffic Server
  Issue Type: Bug
  Components: HTTP
Reporter: Tommy Lee
 Fix For: 5.0.0

 Attachments: tcpdump.txt


 We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some 
 websites that uses Authorization Header.
 We always get 401 ( Unauthorized ) response.
 I'm attaching two debug files. One with ATS-3.2.2 that's working and one with 
 ATS-5.0.0 that's broken.
 Almost the same records.config for both tests.
 I'm looking for changes in source code too. I'll update the issue if I find 
 an answer.
 To devs: Could the question mark after the exchange  can cause that ? This 
 is the only modification between these two versions.
 ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange?
 ATS-5.0.0 GET -  GET http://webmail.candidomendes.edu.br/exchange
 Thanks.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Comment Edited] (TS-2626) Problem with TS-312 - Always share Keep Alive


[ 
https://issues.apache.org/jira/browse/TS-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13933554#comment-13933554
 ] 

Tommy Lee edited comment on TS-2626 at 3/13/14 5:11 PM:


Yep.

We noticed that all sites that does NTLM authentication were broken.



was (Author: tommylee):
Yep.

 Problem with TS-312 - Always share Keep Alive
 -

 Key: TS-2626
 URL: https://issues.apache.org/jira/browse/TS-2626
 Project: Traffic Server
  Issue Type: Bug
  Components: HTTP
Reporter: Tommy Lee
 Fix For: 5.0.0

 Attachments: tcpdump.txt


 We are noted that ATS-5.0.0 from GIT master couldn't authenticate with some 
 websites that uses Authorization Header.
 We always get 401 ( Unauthorized ) response.
 I'm attaching two debug files. One with ATS-3.2.2 that's working and one with 
 ATS-5.0.0 that's broken.
 Almost the same records.config for both tests.
 I'm looking for changes in source code too. I'll update the issue if I find 
 an answer.
 To devs: Could the question mark after the exchange  can cause that ? This 
 is the only modification between these two versions.
 ATS-3.2.2 GET - GET http://webmail.candidomendes.edu.br/exchange?
 ATS-5.0.0 GET -  GET http://webmail.candidomendes.edu.br/exchange
 Thanks.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Assigned] (TS-2626) Problem with TS-312 - Always share Keep Alive + NTLM Authorization