Upgrading from apache-tomcat-8.0.30. to 8.5.35. is causing 403 responses to some POST requests to our API
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 Nov 20 at 21:13
Whitewind617
65117
add a comment |
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 Nov 20 at 21:13
Whitewind617
65117
Do you have an example of the POST request that is failing?
– Julio Daniel Reyes
Nov 21 at 0:37
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
Nov 21 at 16:52
add a comment |
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 Nov 20 at 21:13
Whitewind617
65117
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 Nov 20 at 21:13
Whitewind617
65117
asked Nov 20 at 21:13
Whitewind617
65117
asked Nov 20 at 21:13
Whitewind617
65117
asked Nov 20 at 21:13
Whitewind617
65117
asked Nov 20 at 21:13
Whitewind617
65117
65117
Do you have an example of the POST request that is failing?
– Julio Daniel Reyes
Nov 21 at 0:37
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
Nov 21 at 16:52
add a comment |
Do you have an example of the POST request that is failing?
– Julio Daniel Reyes
Nov 21 at 0:37
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
Nov 21 at 16:52
Do you have an example of the POST request that is failing?
– Julio Daniel Reyes
Nov 21 at 0:37
Do you have an example of the POST request that is failing?
– Julio Daniel Reyes
Nov 21 at 0:37
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
Nov 21 at 16:52
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
Nov 21 at 16:52
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Nov 21 at 0:37
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
Nov 21 at 16:52