garydgregory opened a new pull request, #780:
URL: https://github.com/apache/commons-vfs/pull/780

   Fix UrlFileObject when Java 8's KeepAliveStream reuse causes IOException: 
Stream closed.
   
   doGetContentSize, doGetLastModifiedTime and doGetType now use HEAD for 
HttpURLConnection and call conn.connect() instead of opening and closing a full 
GET InputStream. This removes the body download and avoids the Java 8 
KeepAliveStream reuse that causes IOException: Stream closed.
   
   doGetInputStream now sets Connection: close for HTTP URLs on Java 8 so the 
pooled socket is not reused for the next metadata call.
   
   With this change LastModifiedTests.testGetLastModifiedFile and the 
VfsClassLoaderTests and UrlProviderHttpTest provider tests no longer hit the 
Stream closed error on Java 8 on macOS and Windows.
   
   - [x] Read the [contribution guidelines](CONTRIBUTING.md) for this project.
   - [x] Read the [ASF Generative Tooling 
Guidance](https://www.apache.org/legal/generative-tooling.html) if you use 
Artificial Intelligence (AI).
   - [x] I used AI to research the issue and create the initial version of the 
solution.
   - [x] Run a successful build using the default 
[Maven](https://maven.apache.org/) goal with `mvn`; that's `mvn` on the command 
line by itself.
   - [x] Write unit tests that match behavioral changes, where the tests fail 
if the changes to the runtime are not applied. This may not always be possible, 
but it is a best practice.
   - [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   - [x] Each commit in the pull request should have a meaningful subject line 
and body. Note that a maintainer may squash commits during the merge process.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to