Hello Artem, On what version of JMeter are you seing this ? Thanks
On Tuesday, August 21, 2018, Artem Fedorov <[email protected]> wrote: > HI All > > I configure HTTP Request that use proxy with authentication > > In proxy log I can see, that JMeter *always send 2 requests*: (I used > `squid` in tests) > > 1534844834.248 0 127.0.0.1 TCP_DENIED/407 4056 GET > > http://blazedemo.com/ - HIER_NONE/- text/html > > 1534844834.320 52 127.0.0.1 TCP_MISS/200 8077 GET > > http://blazedemo.com/ artem HIER_DIRECT/54.93.131.97 text/html > > > The first request JMeter send without authentication options, because this > options are create after server got a response with 401/407 code. > > In performance test I'll see the following log: (50 % of all requests are > send without authentication options) - IMO this is incorrect load of proxy > server or we lose a lot of time for create authentication scheme for each > request > > - TCP_DENIED/407 (without proxy authentication) > - TCP_MISS/200 (with proxy authentication) > - TCP_DENIED/407 (without proxy authentication) > - TCP_MISS/200 (with proxy authentication) > - TCP_DENIED/407 (without proxy authentication) > - TCP_MISS/200 (with proxy authentication) > .... > > The first request (the response for this request) use by httpclient for > detect Standard authentication type (Basic/Digest/NTLM/SPNEGO/Kerberos). I > think If we have not dynamic proxy we can *reuse* knowledges about > authentication type in the second and subsequent requests. > After such changes we will see the following log: > > - TCP_DENIED/407 (without proxy authentication) > - TCP_MISS/200 (with proxy authentication) > - TCP_MISS/200 (with proxy authentication) > - TCP_MISS/200 (with proxy authentication) > .... > > What do you think about such changes? If all is OK I can contribute the fix > > > Thanks, > Artem >
