You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Menno Jonkers <jo...@axini.com> on 2016/10/04 14:26:19 UTC
Upgrade to jmeter 3 stops Cache Manager sending If-Modified-Since
Hi,
I have a very basic scenario in JMeter 2.13 that connects to a webapp
using https and basic authentication (w Authorization Manager), then
logs in and starts requesting some often used app urls to measure their
performance and load. It use the Cache Manager and nicely deals with
etags and Last-Modified / If-Modified-Since.
This all worked fine, dealing with a lot of Response code: 304's, but
would break down during a longer run because once in a while JMeter
would omit the Authorization header in its request. Unable to find any
issues/pointers on that, I decided to give JMeter 3.0 r1743807 a go.
But with JMeter 3 and the exact same Test Plan no If-Modified-Since
header is sent out, despite the app still sending Last-Modified headers.
See example header at the bottom.
Rebuilding the plan from scratch in JMeter 3 hasn't made a difference.
Googled quite a bit to no avail. Any suggestions on where to look next?
Thanks!
Menno
Example request/response pair in JMeter 3 below (they all look like this):
JM REQUEST
GET
https://docker-host:32768/test_sets/677acb51-cb06-4af4-9e5a-9b0dfc275bdf/update_list
Cookie Data:
tm_gui_acceptance_test=33fbc47f1c5c3cb55061589b5d1c9109
Request Headers:
Connection: keep-alive
Host: docker-host:32768
User-Agent: Apache-HttpClient/4.5.2 (Java/1.8.0_91)
Authorization: Basic YXhtb2RlbGVyOm1vZGVsZXJwYXNzd29yZA==
APP RESPONSE
HTTP/1.1 200 OK
Date: Tue, 04 Oct 2016 13:59:06 GMT
Server: Apache/2.2.15 (CentOS)
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Cache-Control: max-age=0, private, must-revalidate
X-Request-Id: 0cb8c0ed-82ea-415b-9b7d-40b00470e143
X-Runtime: 0.386244
X-Powered-By: Phusion Passenger 4.0.59
Last-Modified: Tue, 27 Sep 2016 11:59:44 GMT
Status: 200 OK
Vary: Accept-Encoding
Keep-Alive: timeout=15, max=85
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org
Re: Upgrade to jmeter 3 stops Cache Manager sending If-Modified-Since
Posted by Menno Jonkers <jo...@axini.com>.
Hi Felix,
On 04-10-16 17:14, Felix Schumacher wrote:
> Look for vary header handling in the release logs. Those requests
> will not be cached anymore.
Ah, that [1] fully explains it; thank you for your very quick response!
Menno
[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=58079
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org
Re: Upgrade to jmeter 3 stops Cache Manager sending If-Modified-Since
Posted by Felix Schumacher <fe...@internetallee.de>.
Am 4. Oktober 2016 16:26:19 MESZ, schrieb Menno Jonkers <jo...@axini.com>:
>Hi,
>
>I have a very basic scenario in JMeter 2.13 that connects to a webapp
>using https and basic authentication (w Authorization Manager), then
>logs in and starts requesting some often used app urls to measure their
>performance and load. It use the Cache Manager and nicely deals with
>etags and Last-Modified / If-Modified-Since.
>
>This all worked fine, dealing with a lot of Response code: 304's, but
>would break down during a longer run because once in a while JMeter
>would omit the Authorization header in its request. Unable to find any
>issues/pointers on that, I decided to give JMeter 3.0 r1743807 a go.
>
>But with JMeter 3 and the exact same Test Plan no If-Modified-Since
>header is sent out, despite the app still sending Last-Modified
>headers.
>See example header at the bottom.
>
>Rebuilding the plan from scratch in JMeter 3 hasn't made a difference.
>
>Googled quite a bit to no avail. Any suggestions on where to look next?
Look for vary header handling in the release logs. Those requests will not be cached anymore.
Regards,
Felix
>
>Thanks!
>
>Menno
>
>
>
>Example request/response pair in JMeter 3 below (they all look like
>this):
>
>JM REQUEST
>
>GET
>https://docker-host:32768/test_sets/677acb51-cb06-4af4-9e5a-9b0dfc275bdf/update_list
>
>Cookie Data:
>tm_gui_acceptance_test=33fbc47f1c5c3cb55061589b5d1c9109
>
>Request Headers:
>Connection: keep-alive
>Host: docker-host:32768
>User-Agent: Apache-HttpClient/4.5.2 (Java/1.8.0_91)
>Authorization: Basic YXhtb2RlbGVyOm1vZGVsZXJwYXNzd29yZA==
>
>APP RESPONSE
>
>HTTP/1.1 200 OK
>Date: Tue, 04 Oct 2016 13:59:06 GMT
>Server: Apache/2.2.15 (CentOS)
>X-Frame-Options: SAMEORIGIN
>X-XSS-Protection: 1; mode=block
>X-Content-Type-Options: nosniff
>Cache-Control: max-age=0, private, must-revalidate
>X-Request-Id: 0cb8c0ed-82ea-415b-9b7d-40b00470e143
>X-Runtime: 0.386244
>X-Powered-By: Phusion Passenger 4.0.59
>Last-Modified: Tue, 27 Sep 2016 11:59:44 GMT
>Status: 200 OK
>Vary: Accept-Encoding
>Keep-Alive: timeout=15, max=85
>Connection: Keep-Alive
>Transfer-Encoding: chunked
>Content-Type: text/html; charset=utf-8
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
>For additional commands, e-mail: user-help@jmeter.apache.org
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org
For additional commands, e-mail: user-help@jmeter.apache.org