- 19 12月, 2016 5 次提交
-
-
由 Sebastien Deleuze 提交于
-
由 Rossen Stoyanchev 提交于
HandshakeInfo has been promoted to the top-level socket package next to WebSocketSession which exposes it.
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-14832
-
由 Juergen Hoeller 提交于
Issue: SPR-15028
-
- 18 12月, 2016 6 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14527
-
由 Rossen Stoyanchev 提交于
The WebSocketHander adapters are now neutral for client vs server-side use with the adapters for RxNetty and Reactor Netty (server-side only) completely removed. A new HandshakeInfo carries information about the handshake including URI, headers, and principal from the upgrade strategy, to the adapter, and then to the session. WebSocketSession exposes the HandshakeInfo as well reducing its overall number of methods.
-
由 Rossen Stoyanchev 提交于
Move WebSocketMessage factory methods to the WebSocketSession which has the bufferFactory() needed to create message payloads. WebSocketMessage is left with one public constructor. WebSocketMessage exposes convenience retain/releasePayload methods.
-
由 Rossen Stoyanchev 提交于
Expose bufferFactory() at the WebSocketSession level for creating payloads like ReactiveHttpOutputMessage does. Promote getId(), getUri(), and bufferFactory() to the base class WebSocketSessionSupport.
-
由 Rossen Stoyanchev 提交于
-
由 Juergen Hoeller 提交于
Includes consistent use of ResolvableType.resolve() wherever applicable. Issue: SPR-15011
-
- 17 12月, 2016 7 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-14978
-
由 Rossen Stoyanchev 提交于
Apply the new HttpHeaders#getAcceptLanguageAsLocale() in places where it was hardcoded or defaulting. Apply ServerHttpResponse.encodeUrl in RequestContext. Issue: SPR-15024
-
由 Rossen Stoyanchev 提交于
An update on the last commit switching from: List<Locale> getAcceptLanguageAsLocales() to Locale getAcceptLanguageAsLocale() This best supports the scenario for the most preferred Locale. If there is a need to look at the prioritized list of languages it's best to use Locale.filter with the LocaleRange's. This is explained in the Javadoc for getAcceptLanguage(). Issue: SPR-15024
-
由 Rossen Stoyanchev 提交于
The use of Locale.LanguageRange for the Accept-Language header makes sense as it gives the most flexibility for a client to set a weighted list and for a server to do filtering via Locale#filter. This commit adds an additional convenience method that turns the LangugeRange list to a list of Locale's also filtering out a wildcard (i.e. "*"). A List<Locale> is the most basic way to access prefered languages and needed when filtering is not required. Issue: SPR-15024
-
由 Rossen Stoyanchev 提交于
-
由 Stephane Maldini 提交于
-
- 16 12月, 2016 6 次提交
-
-
由 Rossen Stoyanchev 提交于
Consolidate into one method potentially re-using UriComponentsBuilder for the location. Also use StringUtils#applyRelativePath. Issue: SPR-15020
-
由 Rob Winch 提交于
Previously ForwrdedHeaderFilter did not ensure that HttpServletResponse.sendRedirect worked properly based on X-Forwarded-* headers. This commit updates ForwardedHeaderFilter to overrided the HttpServletResponse.sendRedirect method to ensure X-Forwarded-* headers are honored. Issue SPR-15020
-
由 Rossen Stoyanchev 提交于
ServerWebExchange.Builder has an additional Consumer-style shortcut method that accepts a builder for modifying the request. ServerWebExchange and ServerHttpRequest builders have fewer methods, more use-case focused vs matching directly to properties.
-
由 Rossen Stoyanchev 提交于
ServerWebExchange now provides access to "requestParams" as a MulitValueMap with query parameters and form data combined. The combined map is then used for the params condition of @RequestMapping purposes () and also for @RequestParam arguments. Issue: SPR-15000
-
由 Sebastien Deleuze 提交于
Issue: SPR-14536
-
由 Sebastien Deleuze 提交于
Issue: SPR-15024
-
- 15 12月, 2016 16 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-14978
-
由 Juergen Hoeller 提交于
Issue: SPR-15017
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
-
由 Sebastien Deleuze 提交于
Issue: SPR-14992
-
由 Stephane Maldini 提交于
-
由 Rossen Stoyanchev 提交于
Renamed: AbstractListenerFlushProcessor -> AbstractListenerWriteFlushProcessor
-
由 Rossen Stoyanchev 提交于
This is similar to the WriteListener changes on the ServerHttpResponse where we are more naturally exposed to a delayed write. Nevertheless we could also have a delayed read and should be consistent. The early initialization of the RequestBodyPublisher also simplifies the internal implementation a bit.
-
由 Juergen Hoeller 提交于
Issue: SPR-15019
-
由 Juergen Hoeller 提交于
Issue: SPR-15015
-
由 Juergen Hoeller 提交于
Issue: SPR-15010
-
由 Juergen Hoeller 提交于
Issue: SPR-15009
-
由 Juergen Hoeller 提交于
Issue: SPR-14527
-