0.2.8
Features
- Benchmarking Option: Added a benchmarking option on the server to test S3 read and write speeds and latency.
- New Optional Env:
S3_TEST_PERFORMANCE_ON_START
(default:false
)
Add it to the server's environment file astrue
to activate.
- New Optional Env:
- Immediate Request Logging: Introduced optional logging for each request immediately as it is received by the server.
- New Optional Env:
ENABLE_IMMEDIATE_REQUEST_LOGGING
(default:false
)
Set this totrue
to enable immediate logging of requests.
- New Optional Env:
- Ongoing Request Tracking: Added a feature to track and log the number of ongoing requests being processed by the server.
- New Optional Env:
ENABLE_ONGOING_REQUEST_TRACKING
(default:false
)
Set this totrue
to enable tracking and periodic logging of ongoing requests.
- New Optional Env:
Bug Fixes
-
Fixed an issue with Maven remote repositories not returning 404 errors for packages not found, which caused issues for other repositories when part of a virtual repository.
-
Resolved an issue where uploading
package-metadata.xml
to Maven repositories sometimes failed. While this did not affect downloads, it now fully supports the build number feature. -
Added protection against clickjacking, both in JavaScript and through Nginx headers.
Note: If you're using Docker Compose for deployment, please ensure your Nginx configuration file is updated to include the new clickjacking protection. You can find the updated Nginx configuration details here.
-
Fixed virtual repository
Location
header behavior. For example, when a Docker virtual repository received an upload, it previously redirected to the target local repository. Now, it redirects to the virtual repository as expected.