Upgrading from apache-tomcat-8.0.30. to 8.5.35. is causing 403 responses to some POST requests to our API
up vote
0
down vote
favorite
We're running on a pretty outdated version of tomcat at the moment, 8.0.30. We tried to update to version 8.5.35, but we're running into a ton of trouble. Basically MOST of the requests to our REST API work, but some POST requests are returning 403 responses, but we're not sure why.
We eventually had to give up and go back to 8.0.30. for the time being, because we just couldn't figure out what was different in the newer version that would be restricting these calls. We looked in the web.xml and basically every other config file we can think of, but there's no indication of any restrictions, limits, constraints, nothing. Everything else except those 2 POST requests that we identified works, including several other POST requests.
Is there anything about the newer version that could explain why this would be? Downgrading to 8.0.30. is literally the only thing we needed to do to get it working again, everything else is the same.
api tomcat tomcat8 http-status-code-403
asked yesterday
Whitewind617
6017
add a comment |
up vote
0
down vote
favorite
We're running on a pretty outdated version of tomcat at the moment, 8.0.30. We tried to update to version 8.5.35, but we're running into a ton of trouble. Basically MOST of the requests to our REST API work, but some POST requests are returning 403 responses, but we're not sure why.
We eventually had to give up and go back to 8.0.30. for the time being, because we just couldn't figure out what was different in the newer version that would be restricting these calls. We looked in the web.xml and basically every other config file we can think of, but there's no indication of any restrictions, limits, constraints, nothing. Everything else except those 2 POST requests that we identified works, including several other POST requests.
Is there anything about the newer version that could explain why this would be? Downgrading to 8.0.30. is literally the only thing we needed to do to get it working again, everything else is the same.
api tomcat tomcat8 http-status-code-403
asked yesterday
Whitewind617
6017
Do you have an example of the POST request that is failing?
– Julio Daniel Reyes
yesterday
POST /services/availability Sadly I don't have access to the code to see exactly what it's doing, but basically it returns the text "All host services accessible from api.*.*" after it checks to make sure critical services are available. On apache 8.5.35 it just returns 403.
– Whitewind617
11 hours ago
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We're running on a pretty outdated version of tomcat at the moment, 8.0.30. We tried to update to version 8.5.35, but we're running into a ton of trouble. Basically MOST of the requests to our REST API work, but some POST requests are returning 403 responses, but we're not sure why.
We eventually had to give up and go back to 8.0.30. for the time being, because we just couldn't figure out what was different in the newer version that would be restricting these calls. We looked in the web.xml and basically every other config file we can think of, but there's no indication of any restrictions, limits, constraints, nothing. Everything else except those 2 POST requests that we identified works, including several other POST requests.
Is there anything about the newer version that could explain why this would be? Downgrading to 8.0.30. is literally the only thing we needed to do to get it working again, everything else is the same.
api tomcat tomcat8 http-status-code-403
asked yesterday
Whitewind617
6017
We're running on a pretty outdated version of tomcat at the moment, 8.0.30. We tried to update to version 8.5.35, but we're running into a ton of trouble. Basically MOST of the requests to our REST API work, but some POST requests are returning 403 responses, but we're not sure why.
We eventually had to give up and go back to 8.0.30. for the time being, because we just couldn't figure out what was different in the newer version that would be restricting these calls. We looked in the web.xml and basically every other config file we can think of, but there's no indication of any restrictions, limits, constraints, nothing. Everything else except those 2 POST requests that we identified works, including several other POST requests.
Is there anything about the newer version that could explain why this would be? Downgrading to 8.0.30. is literally the only thing we needed to do to get it working again, everything else is the same.
api tomcat tomcat8 http-status-code-403
api tomcat tomcat8 http-status-code-403
asked yesterday
Whitewind617
6017
asked yesterday
Whitewind617
6017
asked yesterday
Whitewind617
6017
asked yesterday
Whitewind617
6017
asked yesterday
Whitewind617
6017
6017
Do you have an example of the POST request that is failing?
– Julio Daniel Reyes
yesterday
POST /services/availability Sadly I don't have access to the code to see exactly what it's doing, but basically it returns the text "All host services accessible from api.*.*" after it checks to make sure critical services are available. On apache 8.5.35 it just returns 403.
– Whitewind617
11 hours ago
add a comment |
Do you have an example of the POST request that is failing?
– Julio Daniel Reyes
yesterday
POST /services/availability Sadly I don't have access to the code to see exactly what it's doing, but basically it returns the text "All host services accessible from api.*.*" after it checks to make sure critical services are available. On apache 8.5.35 it just returns 403.
– Whitewind617
11 hours ago
Do you have an example of the POST request that is failing?
– Julio Daniel Reyes
yesterday
Do you have an example of the POST request that is failing?
– Julio Daniel Reyes
yesterday
POST /services/availability Sadly I don't have access to the code to see exactly what it's doing, but basically it returns the text "All host services accessible from api.*.*" after it checks to make sure critical services are available. On apache 8.5.35 it just returns 403.
– Whitewind617
11 hours ago
POST /services/availability Sadly I don't have access to the code to see exactly what it's doing, but basically it returns the text "All host services accessible from api.*.*" after it checks to make sure critical services are available. On apache 8.5.35 it just returns 403.
– Whitewind617
11 hours ago
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53401614%2fupgrading-from-apache-tomcat-8-0-30-to-8-5-35-is-causing-403-responses-to-some%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Do you have an example of the POST request that is failing?
– Julio Daniel Reyes
yesterday
POST /services/availability Sadly I don't have access to the code to see exactly what it's doing, but basically it returns the text "All host services accessible from api.*.*" after it checks to make sure critical services are available. On apache 8.5.35 it just returns 403.
– Whitewind617
11 hours ago