Deprecated API
Contents
-
ElementDescriptionin favor of
ClientHttpObservationDocumentation.LowCardinalityKeyNames.CLIENT_NAME
; scheduled for removal in 6.2. This will be available both as a low and high cardinality key value.as of 6.0, in favor ofClientHttpResponse.getStatusCode()
as of 6.0, in favor ofPartEvent
andPartEventHttpMessageReader
in favor ofHttpMethod.valueOf(String)
as of Spring Framework 6.0 in favor ofHttpRequest.getMethod()
andHttpMethod.name()
as of 6.0.3, in favor ofAPPLICATION_GRAPHQL_RESPONSE
as of 6.0.3, in favor ofAPPLICATION_GRAPHQL_RESPONSE_VALUE
As of 6.0, with no direct replacementAs of 6.0, with no direct replacementAs of 6.0, in favor ofMimeTypeUtils.sortBySpecificity(List)
As of 6.0, with no direct replacementsince 6.0.8, in favor ofAbstractServerHttpRequest(HttpMethod, URI, String, MultiValueMap)
since 6.0.8, in favor ofAbstractServerHttpRequest(HttpMethod, URI, String, MultiValueMap)
in favor of usingServerWebExchangeContextFilter.getExchange(ContextView)
which accepts aContextView
instead ofContext
, reflecting the fact that theContextView
is needed only for reading.
-
ClassDescriptionas of 6.0, with no direct replacement; scheduled for removal in 6.2as of 5.2.4. See class-level note in
ContentNegotiationManagerFactoryBean
on the deprecation of path extension config options.as of 5.2.4. See class-level note inContentNegotiationManagerFactoryBean
on the deprecation of path extension config options.as of 6.0 in favor ofResponseCookie
-
FieldDescriptionas of 6.0.3, in favor of
APPLICATION_GRAPHQL_RESPONSE
as of 6.0.3, in favor ofAPPLICATION_GRAPHQL_RESPONSE_VALUE
as of 5.2 in favor ofAPPLICATION_JSON
since major browsers like Chrome now comply with the specification and interpret correctly UTF-8 special characters without requiring acharset=UTF-8
parameter.as of 5.2 in favor ofAPPLICATION_JSON_VALUE
since major browsers like Chrome now comply with the specification and interpret correctly UTF-8 special characters without requiring acharset=UTF-8
parameter.as of 5.2 in favor ofAPPLICATION_PROBLEM_JSON
since major browsers like Chrome now comply with the specification and interpret correctly UTF-8 special characters without requiring acharset=UTF-8
parameter.as of 5.2 in favor ofAPPLICATION_PROBLEM_JSON_VALUE
since major browsers like Chrome now comply with the specification and interpret correctly UTF-8 special characters without requiring acharset=UTF-8
parameter.as of 5.3, see notice onAPPLICATION_STREAM_JSON_VALUE
.as of 5.3 since it originates from the W3C Activity Streams specification which has a more specific purpose and has been since replaced with a different mime type. UseAPPLICATION_NDJSON
as a replacement or any other line-delimited JSON format (e.g. JSON Lines, JSON Text Sequences).As of 6.0, with no direct replacementAs of 6.0, with no direct replacement
-
MethodDescriptionas of 6.0, in favor of
ClientHttpResponse.getStatusCode()
; scheduled for removal in 6.2as of 6.0, in favor ofSocketConfig.Builder.setSoTimeout(Timeout)
, see above.as of 6.0, in favor ofClientHttpResponse.getStatusCode()
as of 5.1.13, useCodecConfigurer.CustomCodecs.register(Object)
orCodecConfigurer.CustomCodecs.registerWithDefaultConfig(Object)
instead.as of 5.1.13, useCodecConfigurer.CustomCodecs.register(Object)
orCodecConfigurer.CustomCodecs.registerWithDefaultConfig(Object)
instead.as of 5.1.13, useCodecConfigurer.CustomCodecs.register(Object)
orCodecConfigurer.CustomCodecs.registerWithDefaultConfig(Object)
instead.as of 5.1.13, useCodecConfigurer.CustomCodecs.register(Object)
orCodecConfigurer.CustomCodecs.registerWithDefaultConfig(Object)
instead.as of 6.0, in favor ofPartEvent
andPartEventHttpMessageReader
since 5.2.3 as per RFC 6266, Appendix B, to be removed in a future release.since 5.2.3 as per RFC 6266, Appendix B, to be removed in a future release.since 5.2.3 as per RFC 6266, Appendix B, to be removed in a future release.since 5.2.3 as per RFC 6266, Appendix B, to be removed in a future release.since 5.2.3 as per RFC 6266, Appendix B, to be removed in a future release.since 5.2.3 as per RFC 6266, Appendix B, to be removed in a future release.since 5.2.3 as per RFC 6266, Appendix B, to be removed in a future release.since 5.2.3 as per RFC 6266, Appendix B, to be removed in a future release.in favor ofHttpMethod.valueOf(String)
as of Spring Framework 6.0 in favor ofHttpRequest.getMethod()
andHttpMethod.name()
as of 5.3, in favor of invokingHttpStatus.series()
directlyAs of 6.0, with no direct replacementAs of 6.0, in favor ofMimeTypeUtils.sortBySpecificity(List)
As of 6.0, in favor ofMimeTypeUtils.sortBySpecificity(List)
as of 6.0, in favor ofResponseEntity.getStatusCode()
; scheduled for removal in 7.0originally introduced for Undertow to stop write notifications when no data is available, but deprecated as of 5.0.6 since constant switching on every requested item causes a significant slowdown.as of 6.0, in favor ofServerHttpResponse.getStatusCode()
as of 5.2.4. See class-level note on the deprecation of path extension config options. As there is no replacement for this method, in 5.2.x it is necessary to set it tofalse
. In 5.3 the default changes tofalse
and use of this property becomes unnecessary.as of 5.2.4. See class-level note on the deprecation of path extension config options.as of 5.0, in favor ofContentNegotiationManagerFactoryBean.setUseRegisteredExtensionsOnly(boolean)
, which has reverse behavior.as of 5.0, in favor ofAbstractMappingContentNegotiationStrategy.setUseRegisteredExtensionsOnly(boolean)
.as of 6.0, in favor ofRestClientResponseException.getStatusCode()
as of 6.0, in favor ofUnknownContentTypeException.getStatusCode()
as of 5.2, same-origin checks are performed directly byCorsUtils.isCorsRequest(org.springframework.http.server.reactive.ServerHttpRequest)
as of 5.3 in favor of usingUrlBasedCorsConfigurationSource.setUrlPathHelper(UrlPathHelper)
, if at all. For further details, please seeUrlBasedCorsConfigurationSource.setAllowInitLookupPath(boolean)
.as of 5.3 in favor ofUrlPathHelper.PATH_ATTRIBUTE
.as of 5.3 in favor of usingUrlBasedCorsConfigurationSource.setUrlPathHelper(UrlPathHelper)
, if at all. For further details, please seeUrlBasedCorsConfigurationSource.setAllowInitLookupPath(boolean)
.as of 5.3 in favor of usingUrlBasedCorsConfigurationSource.setUrlPathHelper(UrlPathHelper)
, if at all. For further details, please seeUrlBasedCorsConfigurationSource.setAllowInitLookupPath(boolean)
.in favor of usingServerWebExchangeContextFilter.getExchange(ContextView)
which accepts aContextView
instead ofContext
, reflecting the fact that theContextView
is needed only for reading.as of 6.0 without a replacement; once removed, the default model will always be ignored on redirectas of 6.0, in favor ofResponseStatusExceptionHandler.determineStatus(Throwable)
as of 6.0 in favor ofMethodNotAllowedException.getHeaders()
as of 6.0 in favor ofNotAcceptableStatusException.getHeaders()
as of 6.0 in favor ofResponseStatusException.getHeaders()
as of 6.0 in favor ofUnsupportedMediaTypeStatusException.getHeaders()
as of 6.0 together withPathPatternParser.setMatchOptionalTrailingSeparator(boolean)
.transparent support for trailing slashes is deprecated as of 6.0 in favor of configuring explicit redirects through a proxy, Servlet/web filter, or a controller.as of 5.3 in favor of usingUrlPathHelper.resolveAndCacheLookupPath(HttpServletRequest)
andUrlPathHelper.getResolvedLookupPath(ServletRequest)
.
-
ConstructorDescriptionas of 5.2, in favor of
JettyClientHttpConnector(HttpClient, JettyResourceFactory)
as of 5.1, in favor ofHttpMessageNotReadableException(String, HttpInputMessage)
as of 5.1, in favor ofHttpMessageNotReadableException(String, Throwable, HttpInputMessage)
since 6.0.8, in favor ofAbstractServerHttpRequest(HttpMethod, URI, String, MultiValueMap)
since 6.0.8, in favor ofAbstractServerHttpRequest(HttpMethod, URI, String, MultiValueMap)
as of 6.0as of 6.0
-
Enum ConstantDescriptionin favor of
ClientHttpObservationDocumentation.LowCardinalityKeyNames.CLIENT_NAME
; scheduled for removal in 6.2. This will be available both as a low and high cardinality key value.in favor ofHttpStatus.EARLY_HINTS
which will be returned fromHttpStatus.valueOf(103)
in favor ofHttpStatus.FOUND
which will be returned fromHttpStatus.valueOf(302)
in favor ofHttpStatus.PAYLOAD_TOO_LARGE
which will be returned fromHttpStatus.valueOf(413)
in favor ofHttpStatus.URI_TOO_LONG
which will be returned fromHttpStatus.valueOf(414)
due to security concerns regarding in-band configuration of a proxy
SocketConfig.Builder.setSoTimeout(Timeout)
, see above.