- 07 11月, 2015 4 次提交
-
-
由 Rossen Stoyanchev 提交于
This commit expands the range of whitelisted extensions by checking if an extension can be resolved to image/*, audo/*, video/*, as well as any content type that ends with +xml. Issue: SPR-13643
-
由 Rossen Stoyanchev 提交于
We know skip the Content-Disposition header for any extension if the chosen request mapping explicitly contains the URl extension. Issue: SPR-13629
-
由 Brian Clozel 提交于
Prior to this change, the HttpEntityMethodProcessor would try to process conditional requests that are undefined by the spec, such as: * an HTTP GET request with "If-None-Match:*" * a request with both "If-None-Match" and "If-Match" * a request with both "If-None-Match" and "If-Unmodified-Since" This commit skips the processing of those requests as conditional requests and continues with normal request handling. Issue: SPR-13626
-
由 Juergen Hoeller 提交于
-
- 06 11月, 2015 6 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-13530
-
由 Rossen Stoyanchev 提交于
Issue: SPR-13531
-
由 Rossen Stoyanchev 提交于
Issue: SPR-13642
-
由 Rossen Stoyanchev 提交于
Issue: SPR-13643
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-13621
-
- 05 11月, 2015 8 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-13621
-
由 Rossen Stoyanchev 提交于
The URI template is now manually parsed vs using a regex to extract URI variable names and to create a pattern for matching to actual URLs. This provides more control to deal with nested curly braces. Issue: SPR-13627
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-13621
-
由 Juergen Hoeller 提交于
AnnotatedElementUtils consistently operates on actual annotation type if available (for performance reasons) The goal is to avoid String name comparisons in favor of annotation type identity checks wherever possible. Also, we avoid double getDeclaredAnnotations/getAnnotations checks on anything other than Classes now, since we'd just get the same result in a fresh array. Issue: SPR-13621
-
由 Juergen Hoeller 提交于
Issue: SPR-13621
-
由 Phillip Webb 提交于
Improve the performance of the `getMergedAnnotationAttributes` and `isAnnotated` methods in `AnnotatedElementUtils` by returning immediately when the element had no annotations. Issue: SPR-13621
-
- 03 11月, 2015 7 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-13621
-
由 Sebastien Deleuze 提交于
Add new MediaType.APPLICATION_JSON_UTF8 and MediaType.APPLICATION_JSON_UTF8_VALUE constants for "application/json;charset=UTF-8" content type in order to make it easier to override @RequestMapping "produces" attribute without losing the default JSON charset (UTF-8). Issue: SPR-13600
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-13621
-
由 Juergen Hoeller 提交于
Issue: SPR-13634
-
由 Stephane Nicoll 提交于
Issue: SPR-13633
-
由 Rossen Stoyanchev 提交于
Issue: SPR-13629
-
- 02 11月, 2015 6 次提交
-
-
由 Stephane Nicoll 提交于
Issue: SPR-13633
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-13628
-
由 Juergen Hoeller 提交于
Issue: SPR-13611
-
由 Sebastien Deleuze 提交于
Issue: SPR-13596
-
由 Sebastien Deleuze 提交于
Issue: SPR-13600
-
- 01 11月, 2015 2 次提交
-
-
由 Stephane Nicoll 提交于
* pr/908: Fix typo
-
由 Hasan Kara 提交于
Closes gh-908
-
- 30 10月, 2015 5 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
Refine the approach of having <mvc:view-resolvers> detect and use the ContentNegotiationManager instance registered with <mvc:annotation-driven> introduced in the last commit. Issue: SPR-13559
-
由 Rossen Stoyanchev 提交于
The <mvc:annotation-driven> element now adds an alias when a ContentNegotiationManager bean is registered with a custom name. This helps <mvc:view-resolvers> to more reliably find such a custom ContentNegotiationManager. Issue: SPR-13559
-
由 Rossen Stoyanchev 提交于
Issue: SPR-13234
-
由 Hronom 提交于
Issue: SPR-13607
-
- 29 10月, 2015 2 次提交
-
-
由 Brian Clozel 提交于
Prior to this change, serving resources with ResourceHttpRequestHandler could result in NPE when requesting an existing folder located in a JAR. This commit swallows those exceptions, as it is not possible to foresee those cases without reading the actual resource. This result in a HTTP 200 response with a zero Content-Length instead of a HTTP 500 internal exception. Issue: SPR-13620
-
由 Rossen Stoyanchev 提交于
Issue: SPR-13615
-