We need to keep support for 3xx where the redirect is disabled. In our case 3xx response code is defined to have a different meaning in our specification. So we need continued support for disabling the redirect for 3xx response code.
We are using .disableFollowRedirect() and want to ensure there is no plans to deprecate this feature in the future.
In our case 3xx response code is defined to have a different meaning in our specification.
What do you mean exactly?
Please elaborate.
3XX has been determined to mean that data is available, process is complete. We do not redirect on 3XX and I have seen other specifications that behave similarly. I want to make certain that this functionality is not deprecated.
3XX has been determined to mean that data is available, process is complete.
It looks to me you’re violating the HTTP specification.
IMHO, you could have used 2XX status codes with extra information in HTTP headers or in the response body.
I have seen other specifications that behave similarly
Could you please share some pointers? If some widely known technologies do behave like this, you would have a fair point.
I want to make certain that this functionality is not deprecated.
First, deprecating would enforce proper usage. Over the years, we’ve seen many times people using disableFollowRedirect so that they could parse the Location header, instead of using the currentLocation and currentLocationRegex checks. Extra support work for us.
Then, we traditionally have a policy of abiding to the HTTP specifications and rejecting supporting home made hacks and specs violations. Better fix issues upstream than work around them downstream on our side and bear the costs.
These are not specs that we can change as they are in contract with partners. I have been tasked with assisting the teams to use gatling. As I might agree that this strange, it is what it is and I need to make certain that we have continued gatling support.
Hello Calvin,
Appreciate the feedback. We’ll take it into account with our customer base, who we plan our future roadmap with. For transparency our process is determined by what will provide the most usability and support of our Gatling Enterprise customers. In the current case we can’t guarantee support ongoing for this unless it’s critical for other Gatling customers as well.
All the best,
Pete
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.