Spring Boot in Cloud Foundry (PCF) disable Whitelabel Error Page
up vote
1
down vote
favorite
Related question:
Spring Boot Remove Whitelabel Error Page
For my case,
I disabled whitelabel by setting whitelabel.enabled = false
, and I also exclude ErrorMvcAutoConfiguration. It worked in regular spring boot service. But I deployed the same service on PCF cloud foundry, then spring still want to redirect error to /error page.
Any help and suggestion is welcome.
Edit:
I added exclude annotation on Application, then it works on PCF.
Previously I added exclude configuration in application.yml, then it didn't work on PCF
spring spring-mvc spring-boot cloudfoundry pcf
add a comment |
up vote
1
down vote
favorite
Related question:
Spring Boot Remove Whitelabel Error Page
For my case,
I disabled whitelabel by setting whitelabel.enabled = false
, and I also exclude ErrorMvcAutoConfiguration. It worked in regular spring boot service. But I deployed the same service on PCF cloud foundry, then spring still want to redirect error to /error page.
Any help and suggestion is welcome.
Edit:
I added exclude annotation on Application, then it works on PCF.
Previously I added exclude configuration in application.yml, then it didn't work on PCF
spring spring-mvc spring-boot cloudfoundry pcf
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Related question:
Spring Boot Remove Whitelabel Error Page
For my case,
I disabled whitelabel by setting whitelabel.enabled = false
, and I also exclude ErrorMvcAutoConfiguration. It worked in regular spring boot service. But I deployed the same service on PCF cloud foundry, then spring still want to redirect error to /error page.
Any help and suggestion is welcome.
Edit:
I added exclude annotation on Application, then it works on PCF.
Previously I added exclude configuration in application.yml, then it didn't work on PCF
spring spring-mvc spring-boot cloudfoundry pcf
Related question:
Spring Boot Remove Whitelabel Error Page
For my case,
I disabled whitelabel by setting whitelabel.enabled = false
, and I also exclude ErrorMvcAutoConfiguration. It worked in regular spring boot service. But I deployed the same service on PCF cloud foundry, then spring still want to redirect error to /error page.
Any help and suggestion is welcome.
Edit:
I added exclude annotation on Application, then it works on PCF.
Previously I added exclude configuration in application.yml, then it didn't work on PCF
spring spring-mvc spring-boot cloudfoundry pcf
spring spring-mvc spring-boot cloudfoundry pcf
edited Nov 21 at 22:05
mpromonet
6,120103764
6,120103764
asked Nov 19 at 21:16
Linden X. Quan
166
166
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
You need to create a separate endpoint /error
and then handle it in the method. I would suggest you to maintain a separate controller
infact. My code would look something like this
@RestController
@RequestMapping(path = "/error")
public class ErrorController {
@ApiOperation(value = "Error Page", notes = "Error Page")
@GetMapping
public String error() {
return "Some Error Occurred and I will Graciously show the Error"
}
}
i don't need /error . I just want to return corresponding http status code, when error occor. There is no other way?
– Linden X. Quan
Nov 20 at 11:20
add a comment |
up vote
0
down vote
It turns out circuit breaker service set exclusion property first, than local application.yml didn't take effect. If I add exclusion property in repo, then it take preference.
I feel this is kind of spring bug, since exclusion is list, it should include all items, instead of taking the first configuration only.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
You need to create a separate endpoint /error
and then handle it in the method. I would suggest you to maintain a separate controller
infact. My code would look something like this
@RestController
@RequestMapping(path = "/error")
public class ErrorController {
@ApiOperation(value = "Error Page", notes = "Error Page")
@GetMapping
public String error() {
return "Some Error Occurred and I will Graciously show the Error"
}
}
i don't need /error . I just want to return corresponding http status code, when error occor. There is no other way?
– Linden X. Quan
Nov 20 at 11:20
add a comment |
up vote
0
down vote
You need to create a separate endpoint /error
and then handle it in the method. I would suggest you to maintain a separate controller
infact. My code would look something like this
@RestController
@RequestMapping(path = "/error")
public class ErrorController {
@ApiOperation(value = "Error Page", notes = "Error Page")
@GetMapping
public String error() {
return "Some Error Occurred and I will Graciously show the Error"
}
}
i don't need /error . I just want to return corresponding http status code, when error occor. There is no other way?
– Linden X. Quan
Nov 20 at 11:20
add a comment |
up vote
0
down vote
up vote
0
down vote
You need to create a separate endpoint /error
and then handle it in the method. I would suggest you to maintain a separate controller
infact. My code would look something like this
@RestController
@RequestMapping(path = "/error")
public class ErrorController {
@ApiOperation(value = "Error Page", notes = "Error Page")
@GetMapping
public String error() {
return "Some Error Occurred and I will Graciously show the Error"
}
}
You need to create a separate endpoint /error
and then handle it in the method. I would suggest you to maintain a separate controller
infact. My code would look something like this
@RestController
@RequestMapping(path = "/error")
public class ErrorController {
@ApiOperation(value = "Error Page", notes = "Error Page")
@GetMapping
public String error() {
return "Some Error Occurred and I will Graciously show the Error"
}
}
answered Nov 20 at 6:23
Arun
1,27332051
1,27332051
i don't need /error . I just want to return corresponding http status code, when error occor. There is no other way?
– Linden X. Quan
Nov 20 at 11:20
add a comment |
i don't need /error . I just want to return corresponding http status code, when error occor. There is no other way?
– Linden X. Quan
Nov 20 at 11:20
i don't need /error . I just want to return corresponding http status code, when error occor. There is no other way?
– Linden X. Quan
Nov 20 at 11:20
i don't need /error . I just want to return corresponding http status code, when error occor. There is no other way?
– Linden X. Quan
Nov 20 at 11:20
add a comment |
up vote
0
down vote
It turns out circuit breaker service set exclusion property first, than local application.yml didn't take effect. If I add exclusion property in repo, then it take preference.
I feel this is kind of spring bug, since exclusion is list, it should include all items, instead of taking the first configuration only.
add a comment |
up vote
0
down vote
It turns out circuit breaker service set exclusion property first, than local application.yml didn't take effect. If I add exclusion property in repo, then it take preference.
I feel this is kind of spring bug, since exclusion is list, it should include all items, instead of taking the first configuration only.
add a comment |
up vote
0
down vote
up vote
0
down vote
It turns out circuit breaker service set exclusion property first, than local application.yml didn't take effect. If I add exclusion property in repo, then it take preference.
I feel this is kind of spring bug, since exclusion is list, it should include all items, instead of taking the first configuration only.
It turns out circuit breaker service set exclusion property first, than local application.yml didn't take effect. If I add exclusion property in repo, then it take preference.
I feel this is kind of spring bug, since exclusion is list, it should include all items, instead of taking the first configuration only.
answered Nov 20 at 15:08
Linden X. Quan
166
166
add a comment |
add a comment |
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%2f53382760%2fspring-boot-in-cloud-foundry-pcf-disable-whitelabel-error-page%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