[jira] [Comment Edited] (HTTPCLIENT-1920) Cached HEAD requests without response body

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490842#comment-16490842 ] Jon Moore edited comment on HTTPCLIENT-1920 at 5/25/18 3:04 PM: Well,

[jira] [Comment Edited] (HTTPCLIENT-1920) Cached HEAD requests without response body

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490842#comment-16490842 ] Jon Moore edited comment on HTTPCLIENT-1920 at 5/25/18 3:04 PM: Well,

[jira] [Commented] (HTTPCLIENT-1920) Cached HEAD requests without response body

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16490842#comment-16490842 ] Jon Moore commented on HTTPCLIENT-1920: --- Well, I haven't looked at the codebase myself in

[jira] [Commented] (HTTPCLIENT-1920) Cached HEAD requests without response body

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464311#comment-16464311 ] Jon Moore commented on HTTPCLIENT-1920: --- Please update your PR if you're willing! I'm more able

[jira] [Comment Edited] (HTTPCLIENT-1920) Cached HEAD requests without response body

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464174#comment-16464174 ] Jon Moore edited comment on HTTPCLIENT-1920 at 5/4/18 5:32 PM: --- Ok, as

[jira] [Commented] (HTTPCLIENT-1920) Cached HEAD requests without response body

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16464174#comment-16464174 ] Jon Moore commented on HTTPCLIENT-1920: --- Ok, as I understand it, the bug occurs when we have a

[jira] [Commented] (HTTPCLIENT-1920) Cached HEAD requests without response body

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16458599#comment-16458599 ] Jon Moore commented on HTTPCLIENT-1920: --- Yes, I'll try to take a look sometime this week. >

[jira] [Commented] (HTTPCLIENT-1828) HttpDelete does not extend HttpEntityEnclosingRequestBase

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15905217#comment-15905217 ] Jon Moore commented on HTTPCLIENT-1828: --- I'll toss my 2c in, hoping to be helpful. Because new

[jira] [Commented] (HTTPCLIENT-1789) 200 Response with Vary header does not invalidate cached 404 response without

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702588#comment-15702588 ] Jon Moore commented on HTTPCLIENT-1789: --- Oh, I agree--you're quite right. I should have said

[jira] [Comment Edited] (HTTPCLIENT-1789) 200 Response with Vary header does not invalidate cached 404 response without

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702356#comment-15702356 ] Jon Moore edited comment on HTTPCLIENT-1789 at 11/28/16 5:34 PM: - I

[jira] [Updated] (HTTPCLIENT-1789) 200 Response with Vary header does not invalidate cached 404 response without

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore updated HTTPCLIENT-1789: -- Priority: Minor (was: Major) > 200 Response with Vary header does not invalidate cached

[jira] [Assigned] (HTTPCLIENT-1789) 200 Response with Vary header does not invalidate cached 404 response without

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore reassigned HTTPCLIENT-1789: - Assignee: Jon Moore > 200 Response with Vary header does not invalidate cached 404

[jira] [Commented] (HTTPCLIENT-1789) 200 Response with Vary header does not invalidate cached 404 response without

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15702356#comment-15702356 ] Jon Moore commented on HTTPCLIENT-1789: --- I see what you're saying, and agree this behavior is

[jira] [Commented] (HTTPCLIENT-1755) SNI problem when connecting to nginx

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15373308#comment-15373308 ] Jon Moore commented on HTTPCLIENT-1755: --- [~proeat...@gmail.com] : I think that analysis would

[jira] [Commented] (HTTPCLIENT-1725) Heuristic caching does not work for URIs with a query string

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15172242#comment-15172242 ] Jon Moore commented on HTTPCLIENT-1725: --- This is because of Section 13.9 of RFC 2616:

[jira] [Commented] (HTTPCLIENT-1630) 304 response causes multiple copies of file in cache

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14353359#comment-14353359 ] Jon Moore commented on HTTPCLIENT-1630: --- Are both cache entries in the

[jira] [Commented] (HTTPCLIENT-1601) Tutorial claims that PUT is not idempotent

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14290700#comment-14290700 ] Jon Moore commented on HTTPCLIENT-1601: --- I don't think this is a bug in the

[jira] [Commented] (HTTPCLIENT-1579) CacheValidityPolicy does not correctly handle 304 Not Modified freshness

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208730#comment-14208730 ] Jon Moore commented on HTTPCLIENT-1579: --- Hi, do you have an example

[jira] [Commented] (HTTPCLIENT-1515) Caching responses to HEAD requests

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14177064#comment-14177064 ] Jon Moore commented on HTTPCLIENT-1515: --- Yep, if we are backwards-compatible

[jira] [Commented] (HTTPCLIENT-1515) Caching responses to HEAD requests

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14172829#comment-14172829 ] Jon Moore commented on HTTPCLIENT-1515: --- Sorry I haven't been able to look at

[jira] [Commented] (HTTPCLIENT-1542) Caching HttpClient uses absolute URIs for validation

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14097008#comment-14097008 ] Jon Moore commented on HTTPCLIENT-1542: --- I suspect this is a problem that we

[jira] [Commented] (HTTPCLIENT-1515) Caching responses to HEAD requests

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14029199#comment-14029199 ] Jon Moore commented on HTTPCLIENT-1515: --- [~fx.bonnet]: I'm curious: what part

[jira] [Commented] (HTTPCLIENT-1515) Caching responses to HEAD requests

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14028003#comment-14028003 ] Jon Moore commented on HTTPCLIENT-1515: --- I like the idea of putting the method

[jira] [Commented] (HTTPCLIENT-1515) Caching responses to HEAD requests

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14026520#comment-14026520 ] Jon Moore commented on HTTPCLIENT-1515: --- @Tyrone: thanks for this contribution.

[jira] [Commented] (HTTPCLIENT-1487) CachingHttpClient doesn't persist cache

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13939652#comment-13939652 ] Jon Moore commented on HTTPCLIENT-1487: --- I want to say there was a recent issue

[jira] [Commented] (HTTPCLIENT-1487) CachingHttpClient doesn't persist cache

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13939657#comment-13939657 ] Jon Moore commented on HTTPCLIENT-1487: --- Found it: HTTPCLIENT-1460.

[jira] [Reopened] (HTTPCLIENT-1487) CachingHttpClient doesn't persist cache

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore reopened HTTPCLIENT-1487: --- Assignee: Jon Moore CachingHttpClient doesn't persist cache

[jira] [Resolved] (HTTPCLIENT-1487) CachingHttpClient doesn't persist cache

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore resolved HTTPCLIENT-1487. --- Resolution: Duplicate CachingHttpClient doesn't persist cache

[jira] [Commented] (HTTPCLIENT-1347) gzip responses doubly cached

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13870275#comment-13870275 ] Jon Moore commented on HTTPCLIENT-1347: --- I also need to refresh my memory here,

[jira] [Updated] (HTTPCLIENT-1347) gzip responses doubly cached

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore updated HTTPCLIENT-1347: -- Issue Type: Improvement (was: Bug) I'm reclassifying this as an improvement, rather than

[jira] [Commented] (HTTPCLIENT-1347) gzip responses doubly cached

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13870344#comment-13870344 ] Jon Moore commented on HTTPCLIENT-1347: --- I agree this isn't working as well as

[jira] [Commented] (HTTPCLIENT-1415) Cached entry is not flushed when a response contains a content-location header without an ETag header field

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789081#comment-13789081 ] Jon Moore commented on HTTPCLIENT-1415: --- Hi Kyle, The way the existing

[jira] [Updated] (HTTPCLIENT-1415) Cached entry is not flushed when a response contains a content-location header without an ETag header field

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore updated HTTPCLIENT-1415: -- Issue Type: Improvement (was: Bug) Cached entry is not flushed when a response contains

[jira] [Commented] (HTTPCLIENT-1415) Cached entry is not flushed when a response contains a content-location header without an ETag header field

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13789082#comment-13789082 ] Jon Moore commented on HTTPCLIENT-1415: --- I believe that HTTPCLIENT-1384, once

[jira] [Resolved] (HTTPCLIENT-1415) Cached entry is not flushed when a response contains a content-location header without an ETag header field

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore resolved HTTPCLIENT-1415. --- Resolution: Duplicate Cached entry is not flushed when a response contains a

[jira] [Commented] (HTTPCLIENT-1395) Call the storage implementation only once on a cache miss

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756612#comment-13756612 ] Jon Moore commented on HTTPCLIENT-1395: --- Hi Nikola, I agree that minimizing

[jira] [Created] (HTTPASYNC-53) Weak ETag Validation is Useful on PUT with If-Match

Jon Moore created HTTPASYNC-53: -- Summary: Weak ETag Validation is Useful on PUT with If-Match Key: HTTPASYNC-53 URL: https://issues.apache.org/jira/browse/HTTPASYNC-53 Project: HttpComponents

[jira] [Resolved] (HTTPCLIENT-1371) Weak ETag Validation is Useful On PUT With If-Match

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore resolved HTTPCLIENT-1371. --- Resolution: Fixed Fix Version/s: (was: 4.4 Final) 4.3

[jira] [Commented] (HTTPCLIENT-1371) Weak ETag Validation is Useful On PUT With If-Match

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13754842#comment-13754842 ] Jon Moore commented on HTTPCLIENT-1371: --- I've applied the patch to

[jira] [Commented] (HTTPASYNC-53) Weak ETag Validation is Useful on PUT with If-Match

[ https://issues.apache.org/jira/browse/HTTPASYNC-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13754860#comment-13754860 ] Jon Moore commented on HTTPASYNC-53: This just requires a simple fix in the facade

[jira] [Comment Edited] (HTTPASYNC-53) Weak ETag Validation is Useful on PUT with If-Match

[ https://issues.apache.org/jira/browse/HTTPASYNC-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13754860#comment-13754860 ] Jon Moore edited comment on HTTPASYNC-53 at 8/30/13 4:21 PM: -

[jira] [Commented] (HTTPCLIENT-1371) Weak ETag Validation is Useful On PUT With If-Match

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13753661#comment-13753661 ] Jon Moore commented on HTTPCLIENT-1371: --- @James: Unfortunately, no, I haven't

[jira] [Commented] (HTTPCLIENT-1392) CLONE - redirect error! java.net.URISyntaxException: Illegal character

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13748594#comment-13748594 ] Jon Moore commented on HTTPCLIENT-1392: --- @Saurabh: this is marked resolved as

[jira] [Commented] (HTTPCLIENT-1392) CLONE - redirect error! java.net.URISyntaxException: Illegal character

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13748955#comment-13748955 ] Jon Moore commented on HTTPCLIENT-1392: --- @Saurabh: Browsers may be being

[jira] [Updated] (HTTPCLIENT-1368) stale-if-error request cache directive should also apply to non-revalidatable cache entries

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore updated HTTPCLIENT-1368: -- Priority: Minor (was: Major) Fix Version/s: (was: 4.2.6)

[jira] [Updated] (HTTPCLIENT-1375) Add context attribute when request are processed by an AsynchronousValidator

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore updated HTTPCLIENT-1375: -- Fix Version/s: (was: 4.3 Final) Future Add context attribute

[jira] [Commented] (HTTPCLIENT-1384) Expose CacheInvalidator in CachingHttpClientBuilder

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13735070#comment-13735070 ] Jon Moore commented on HTTPCLIENT-1384: --- Ok, I see what you are getting at, and

[jira] [Updated] (HTTPCLIENT-1373) OPTIONS and TRACE Should Not Invalidate Cache

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore updated HTTPCLIENT-1373: -- Attachment: README.txt OPTIONS and TRACE Should Not Invalidate Cache

[jira] [Updated] (HTTPCLIENT-1373) OPTIONS and TRACE Should Not Invalidate Cache

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore updated HTTPCLIENT-1373: -- Attachment: (was: README.txt) OPTIONS and TRACE Should Not Invalidate Cache

[jira] [Resolved] (HTTPCLIENT-1373) OPTIONS and TRACE Should Not Invalidate Cache

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore resolved HTTPCLIENT-1373. --- Resolution: Fixed Ok, patch merged with trunk. Many thanks for the patch, James!

[jira] [Updated] (HTTPCLIENT-1384) Expose CacheInvalidator in CachingHttpClientBuilder

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore updated HTTPCLIENT-1384: -- Fix Version/s: (was: 4.3 Final) Future Expose

[jira] [Resolved] (HTTPCLIENT-1370) Response to Non-GET Requests Should Never be Cached With the Default Response CachingPolicy

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore resolved HTTPCLIENT-1370. --- Resolution: Fixed Patch merged with trunk. Many thanks, James!

[jira] [Commented] (HTTPCLIENT-1384) Expose CacheInvalidator in CachingHttpClientBuilder

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723909#comment-13723909 ] Jon Moore commented on HTTPCLIENT-1384: --- I think exposing a cache invalidation

[jira] [Commented] (HTTPCLIENT-1361) stale-while-revalidate should work also without last-modified nor etag

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13699440#comment-13699440 ] Jon Moore commented on HTTPCLIENT-1361: --- I'd be happy to review the week of

[jira] [Commented] (HTTPCLIENT-1371) Weak ETag Validation is Useful On PUT With If-Match

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13683426#comment-13683426 ] Jon Moore commented on HTTPCLIENT-1371: --- What are people's thoughts about the

[jira] [Commented] (HTTPASYNC-44) CachingHttpAsyncClient Has Gotten Out Of Sync With CachingExec

[ https://issues.apache.org/jira/browse/HTTPASYNC-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682256#comment-13682256 ] Jon Moore commented on HTTPASYNC-44: I also think there's value to having a cache on

[jira] [Created] (HTTPASYNC-47) Async caching module is not async for cache I/O and does not share enough implementation with synchronous client cache

Jon Moore created HTTPASYNC-47: -- Summary: Async caching module is not async for cache I/O and does not share enough implementation with synchronous client cache Key: HTTPASYNC-47 URL:

[jira] [Commented] (HTTPASYNC-44) CachingHttpAsyncClient Has Gotten Out Of Sync With CachingExec

[ https://issues.apache.org/jira/browse/HTTPASYNC-44?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682261#comment-13682261 ] Jon Moore commented on HTTPASYNC-44: Created HTTPASYNC-47 to track the longer-term

[jira] [Resolved] (HTTPCLIENT-1370) Response to Non-GET Requests Should Never be Cached With the Default Response CachingPolicy

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore resolved HTTPCLIENT-1370. --- Resolution: Not A Problem Response to Non-GET Requests Should Never be Cached With

[jira] [Commented] (HTTPCLIENT-1370) Response to Non-GET Requests Should Never be Cached With the Default Response CachingPolicy

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682322#comment-13682322 ] Jon Moore commented on HTTPCLIENT-1370: --- Hi James, This particular case is

[jira] [Comment Edited] (HTTPCLIENT-1370) Response to Non-GET Requests Should Never be Cached With the Default Response CachingPolicy

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682343#comment-13682343 ] Jon Moore edited comment on HTTPCLIENT-1370 at 6/13/13 3:28 PM:

[jira] [Commented] (HTTPCLIENT-1370) Response to Non-GET Requests Should Never be Cached With the Default Response CachingPolicy

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682343#comment-13682343 ] Jon Moore commented on HTTPCLIENT-1370: --- James, I understand that, but this

[jira] [Commented] (HTTPCLIENT-1370) Response to Non-GET Requests Should Never be Cached With the Default Response CachingPolicy

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682369#comment-13682369 ] Jon Moore commented on HTTPCLIENT-1370: --- Ah, I see. You're pointing out that

[jira] [Commented] (HTTPCLIENT-1370) Response to Non-GET Requests Should Never be Cached With the Default Response CachingPolicy

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13682492#comment-13682492 ] Jon Moore commented on HTTPCLIENT-1370: --- Ah, ok, I get it now. Totally agree

[jira] [Resolved] (HTTPCLIENT-1353) 303 Redirects Should be Cacheable

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore resolved HTTPCLIENT-1353. --- Resolution: Fixed 303 Redirects Should be Cacheable

[jira] [Commented] (HTTPCLIENT-1353) 303 Redirects Should be Cacheable

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679580#comment-13679580 ] Jon Moore commented on HTTPCLIENT-1353: --- Ok, patch to the async client also

[jira] [Created] (HTTPCLIENT-1368) stale-if-error request cache directive should also apply to non-revalidatable cache entries

Jon Moore created HTTPCLIENT-1368: - Summary: stale-if-error request cache directive should also apply to non-revalidatable cache entries Key: HTTPCLIENT-1368 URL:

[jira] [Commented] (HTTPCLIENT-1353) 303 Redirects Should be Cacheable

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13677530#comment-13677530 ] Jon Moore commented on HTTPCLIENT-1353: --- Ok, I merged the first patch (to the

[jira] [Commented] (HTTPCLIENT-1361) stale-while-revalidate should work also without last-modified nor etag

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670242#comment-13670242 ] Jon Moore commented on HTTPCLIENT-1361: --- Validation is defined in RFC2616:

[jira] [Commented] (HTTPCLIENT-1361) stale-while-revalidate should work also without last-modified nor etag

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670270#comment-13670270 ] Jon Moore commented on HTTPCLIENT-1361: --- Just talked to @mnot on Twitter, and

[jira] [Commented] (HTTPCLIENT-1353) 303 Redirects Should be Cacheable

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670382#comment-13670382 ] Jon Moore commented on HTTPCLIENT-1353: --- Ok, great. I'll look at

[jira] [Commented] (HTTPCLIENT-1353) 303 Redirects Should be Cacheable

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658250#comment-13658250 ] Jon Moore commented on HTTPCLIENT-1353: --- I think it's important to note that

[jira] [Updated] (HTTPCLIENT-1353) 303 Redirects Should be Cacheable

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore updated HTTPCLIENT-1353: -- Priority: Minor (was: Major) Assignee: Jon Moore Issue Type: Improvement

[jira] [Commented] (HTTPCLIENT-1353) 303 Redirects Should be Cacheable

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13658573#comment-13658573 ] Jon Moore commented on HTTPCLIENT-1353: --- Ok, then if James can revise his patch

[jira] [Commented] (HTTPCLIENT-1310) Allow background validation to optionally back off after a number of failed requests

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13586141#comment-13586141 ] Jon Moore commented on HTTPCLIENT-1310: --- @fx: 1. The failures here are quite

[jira] [Commented] (HTTPCLIENT-1310) Allow background validation to optionally back off after a number of failed requests

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13581726#comment-13581726 ] Jon Moore commented on HTTPCLIENT-1310: --- I think this is reasonable

[jira] [Commented] (HTTPCLIENT-1290) 304 cached response never reused with If-modified-since conditional requests

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13545822#comment-13545822 ] Jon Moore commented on HTTPCLIENT-1290: --- Actually, in particular, see 13.4 of

[jira] [Commented] (HTTPCLIENT-1263) CachingHttpClient not consuming backend HttpResponse entity causing PoolingClientConnectionManager to become unresponsive

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13502082#comment-13502082 ] Jon Moore commented on HTTPCLIENT-1263: --- I can try to get to this sometime

[jira] [Commented] (HTTPCLIENT-1257) Header location automatically converted to ASCII even though location can contain UTF-8 encoded urls

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13486784#comment-13486784 ] Jon Moore commented on HTTPCLIENT-1257: --- Can you add the wire log section for

[jira] [Closed] (HTTPCLIENT-1256) HttpClient permits man in the middle attacks when using HTTPS

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore closed HTTPCLIENT-1256. - HttpClient permits man in the middle attacks when using HTTPS

[jira] [Commented] (HTTPCLIENT-1256) HttpClient permits man in the middle attacks when using HTTPS

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13485793#comment-13485793 ] Jon Moore commented on HTTPCLIENT-1256: --- Hi Robert, 3.x is more than not under

[jira] [Resolved] (HTTPCLIENT-1256) HttpClient permits man in the middle attacks when using HTTPS

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore resolved HTTPCLIENT-1256. --- Resolution: Won't Fix Unfortunately, the 3.x series is EOL.

[jira] [Commented] (HTTPCLIENT-1248) LaxRedirectStrategy converts POST to GET and throws away body

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13473136#comment-13473136 ] Jon Moore commented on HTTPCLIENT-1248: --- @Justus: This is actually compliant

[jira] [Comment Edited] (HTTPCLIENT-1248) LaxRedirectStrategy converts POST to GET and throws away body

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13473136#comment-13473136 ] Jon Moore edited comment on HTTPCLIENT-1248 at 10/10/12 10:06 AM:

[jira] [Commented] (HTTPCLIENT-1240) Empty HttpParams for cacheable requests

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469472#comment-13469472 ] Jon Moore commented on HTTPCLIENT-1240: --- Hmm. Unfortunately, we can't take a

[jira] [Created] (HTTPCLIENT-1244) convert unit tests for cache module to use Mockito

Jon Moore created HTTPCLIENT-1244: - Summary: convert unit tests for cache module to use Mockito Key: HTTPCLIENT-1244 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1244 Project: HttpComponents

[jira] [Commented] (HTTPCLIENT-1245) org.apache.http.impl.client.cache.memcached.SHA256KeyHashingScheme use of MessageDigest should be synchronized

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469704#comment-13469704 ] Jon Moore commented on HTTPCLIENT-1245: --- If you look at the implementation of

[jira] [Commented] (HTTPCLIENT-1245) org.apache.http.impl.client.cache.memcached.SHA256KeyHashingScheme use of MessageDigest should be synchronized

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13469711#comment-13469711 ] Jon Moore commented on HTTPCLIENT-1245: --- Just to be clear, I'm open to the fact

[jira] [Commented] (HTTPCLIENT-1245) org.apache.http.impl.client.cache.memcached.SHA256KeyHashingScheme use of MessageDigest should be synchronized

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13470003#comment-13470003 ] Jon Moore commented on HTTPCLIENT-1245: --- No problem. Glad you're using the

[jira] [Assigned] (HTTPCLIENT-1225) A cacheable no-body response causes a NPE when that cache entry is hit

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore reassigned HTTPCLIENT-1225: - Assignee: Jon Moore A cacheable no-body response causes a NPE when that cache

[jira] [Closed] (HTTPCLIENT-1223) Cache could be more aggressive on cache invalidations from Content-Location

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore closed HTTPCLIENT-1223. - Cache could be more aggressive on cache invalidations from Content-Location

[jira] [Commented] (HTTPASYNC-17) org.apache.http.impl.client.cache.CachingHttpClient should have an nio counterpart: CachingHttpAsyncClient

[ https://issues.apache.org/jira/browse/HTTPASYNC-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13426744#comment-13426744 ] Jon Moore commented on HTTPASYNC-17: @Oleg: agree we should extract the common code

[jira] [Updated] (HTTPCLIENT-1202) ResponseCachingPolicy should honor explicit cache-control directives for non-recognized status codes

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore updated HTTPCLIENT-1202: -- Priority: Minor (was: Major) Fix Version/s: 4.2.1 Assignee: Jon Moore

[jira] [Commented] (HTTPCLIENT-1202) ResponseCachingPolicy should honor explicit cache-control directives for non-recognized status codes

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291020#comment-13291020 ] Jon Moore commented on HTTPCLIENT-1202: --- @Joshua: Fixed in trunk; please see if

[jira] [Resolved] (HTTPCLIENT-1202) ResponseCachingPolicy should honor explicit cache-control directives for non-recognized status codes

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore resolved HTTPCLIENT-1202. --- Resolution: Fixed ResponseCachingPolicy should honor explicit cache-control

[jira] [Commented] (HTTPCLIENT-1202) ResponseCachingPolicy should honor explicit cache-control directives for non-recognized status codes

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291107#comment-13291107 ] Jon Moore commented on HTTPCLIENT-1202: --- Hi Joshua. To the best of my

[jira] [Commented] (HTTPCLIENT-1202) ResponseCachingPolicy should honor explicit cache-control directives for non-recognized status codes

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13291241#comment-13291241 ] Jon Moore commented on HTTPCLIENT-1202: --- Ok, I'll take a look, although I think

[jira] [Commented] (HTTPCLIENT-1201) provide basic documentation in an obvious place

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1327#comment-1327 ] Jon Moore commented on HTTPCLIENT-1201: --- Hi Miles, Try checking out the whole

[jira] [Resolved] (HTTPCLIENT-1198) HttpHost is not set in HttpContext in CachingHttpClient

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jon Moore resolved HTTPCLIENT-1198. --- Resolution: Fixed Fix Version/s: 4.2.1 @Ilirjan: I just checked a fix into

[jira] [Commented] (HTTPCLIENT-1198) HttpHost is not set in HttpContext in CachingHttpClient

[ https://issues.apache.org/jira/browse/HTTPCLIENT-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13287630#comment-13287630 ] Jon Moore commented on HTTPCLIENT-1198: --- One final comment here: for the cache

  1   2   >