[Bug 54598] New: Exceeding httpsampler.max_redirects rise an exception

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=54598

            Bug ID: 54598
           Summary: Exceeding httpsampler.max_redirects rise an exception
           Product: JMeter
           Version: 2.9
          Hardware: PC
                OS: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTTP
          Assignee: issues@jmeter.apache.org
          Reporter: paontis@gmail.com
    Classification: Unclassified

Created attachment 29982
  --> https://issues.apache.org/bugzilla/attachment.cgi?id=29982&action=edit
Exception trace displayed in the sample response

Consider an HTTP Request which generates two HTTP 302 Redirects.
I am interested only in the first redirect, because the second one points to an
external system, which is not currently under test.
So in the user.properties I set httpsampler.max_redirects=1 expecting JMeter
just to stop after the first redirect.

Running the test, after the first redirect (performing the second redirection)
the following exception is raised:
java.io.IOException: Exceeeded maximum number of redirects: 1
and the sample results to be 'failed'

I think that to verify that a request do not generates more than X
redirections, it should be available a specific Assertion.
When i set a property in the user.properties, i just expect to modify the
JMeter behaviour, in this case to stop after X redirections but without errors
and, however, without unhandled exceptions.

See attachment max_redirects.png

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 54598] Exceeding httpsampler.max_redirects rise an exception

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=54598

--- Comment #3 from Sebb <se...@apache.org> ---
There needs to be a maximum redirect limit, otherwise JMeter could crash with
out of memory or similar.

That is the purpose of httpsampler.max_redirects.
Changing its meaning could affect some tests.

If you want to raise an enhancement request to add support for limited redirect
following, then please do so and it will be considered as such.

The behaviour of httpsampler.max_redirects will not be changed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 54598] Exceeding httpsampler.max_redirects rise an exception

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=54598

--- Comment #4 from paontis@gmail.com ---
Ok, thanks a lot for the explanation!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 54598] Exceeding httpsampler.max_redirects rise an exception

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=54598

--- Comment #2 from paontis@gmail.com ---
I am not asking any question.
I am stating that rising an unhandled exception it is a bug.

I want the redirects to be followed, but limit them to two redirects.

So in my opinion this is a bug.
Otherwise, i should have not reported it here.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 54598] Exceeding httpsampler.max_redirects rise an exception

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=54598

Sebb <se...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Sebb <se...@apache.org> ---
Bugzilla is not a support forum; please ask such questions on the user list
first in futuer.

The property httpsampler.max_redirects is used to prevent a redirect cycle.

If you don't want redirects to be followed, turn that option off.

Please follow up on the user list.

-- 
You are receiving this mail because:
You are the assignee for the bug.