v3.0.2

Fixes:

• Using vhost-style requests would resolve with a bucket name of undefined (#421)

Tooling:

• Update dependency aws-sdk to v2.427.0 (#423)

v3.0.0-1

Breaking changes:

• You must now specify a specific set of credentials for signed requests to work. Use S3RVER for both the Access Key ID and Secret Access Key.
• The underlying app returned by new S3rver(opts) is now a Koa instance. (#391)
  • Additionally, some constructor options have been renamed and moved.
• s3rver.run([callback]) no longer returns a HTTP server instance. The HTTP server created is set at s3rver.httpServer.
• s3rver.getMiddleware() was renamed to just s3rver.middleware()
• The RxJS Observable s3rver.s3Event has been removed in interest of keeping the library lightweight. Use s3rver.on('event', handler) instead.
• Bucket features are no longer globally configured. CORS and static website configurations can be set through S3's API or in custom bucket configurations initialized at server startup.

Features:

• You can now have preconfigured buckets created at server startup via opts.configureBuckets (or --configure-bucket in the CLI). Existing buckets will have their configurations updated with a warning.
• Support the S3 cors and website REST APIs
  • This comes with per-bucket configuration of these features (and any others implemented in the future) (#397)
• Support for following redirects specified by x-amz-website-redirect-location metadata (#397)
• Stubs for most other bucket actions (they now report 501 Unimplemented)
• Signature verification and presigned URLs (#419)
• Support specifying custom metadata through query parameters (#419)
• Overriding response headers in presigned requests via response-* query params (#419)

Fixes:

• Support more regions for buckets specified via subdomain
  • For example, eu-west-1 only offers an endpoint at s3.eu-west-1.amazonaws.com (with a period instead of a hyphen after .s3)
• Buckets operating in "website mode" behave more predictably and should always serve XML-formatted API responses. Real S3 accomplishes this by having totally separate listeners at the DNS/server level, we reconcile this with a single listener by inpecting the Host header and accepted content type.
  • This fixes the "Unexpected token ..." errors reported by the AWS SDK
  • More specifically, S3rver will prioritize Host and fall back to the Accept header. For example, when applicable, requests with
    Host: <bucket-name>.s3[.<region>].amazonaws.com
    will always have XML-formatted responses, but requests with
    Host: <bucket-name>.s3-website.<region>.amazonaws.com
    will always have HTML-formatted responses. Otherwise, S3rver will return HTML when Accept: text/html is present.
• Virtual Host-style requests (specifying Host: <bucket-name>) should work regardless of static website configuration
• Metadata missing from multipart uploads (#397)
• Querying an object for a key stored without a trailing slash would incorrectly match keys stored with one (#397)
• Can't store keys using reserved characters under Windows (#420)
• All error responses reported by S3rver have been revisited and revised to look nearly identical to real S3

v2.2.9

Features:

• Validate and report illegal AllowedMethods in CORS configurations (#385)

Fixes:

• Fix ranged requests on Windows and other environments (#384)
• Return error if a request to delete multiple objects has no objects specified (#386)
• Fix empty directory cleanup when deleting a deeply nested key (#387)

Tooling:

• Update Winston to v3 (#258)
• Update concat-stream to v2 (#356)
• Update xmlbuilder to (#398)
• Update Mocha to v6 (#401)
• Update dependencies (#378 #379 #380 #381 #382 #388 #389 #393 #394 #395 #396 #399 #400 #403 #404 #405 #406 #407 #408 #409 #410 #411 #412 #413 #414 #415)

v2.2.8

Fixes:

• Fix range handling for oversized and out of range situations #373

Tooling:

• Update dependencies #351 #352 #353 #354 #355 #357 #358 #359 #360 #361 #362 #363 #364 #365 #366 #367 #368 #369 #370 #371 #377

v2.2.7

Fixes:

• Exit with non-zero status with misconfigured data directory #325
• Handle the case where the access-control-request-header is not provided #347

Tooling:

• Update dependencies #313 #314 #315 #316 #317 #318 #319 #320 #321 #322 #323 #324 #326 #327 #328 #329 #331 #332 #335 #336 #337 #338 #339 #340 #341 #342 #343 #344 #345 #348 #349 #350

v2.2.6

Fixes:

• S3Event's eventTime should always be a new date (#290)

Tooling:

• Update dependencies #285 #286 #287 #291 #292 #294 #295 #296 #297 #298 #299 #300 #302 #303 #304 #305 #307 #308 #309 #311 #312

v2.2.5

Fixes:

• Avoid monkeypatching the close method on the returned server instance #275
• Use RxJS pipeable operators #276

Tooling:

• Update dependencies #277 #282 #284 #283 #281 #280 #279 #278 #268 #248 #268 #248 #273 #272 #271 #270 #267 #266 #265 #264 #263 #262 #261 #259 #257 #256 #255 #254 #253 #252 #251 #250 #249 #247 #246 #245 #244 #243 #242 #241 #240 #239 #238 #237 #236 #235 #234 #233 #232 #229 #228

v2.2.4

Fixes:

• Sending empty list of objects with s3.deleteObjects causes a crash. (#223)
• Update dependency xmlbuilder to version 10.0.0 (#222)
• Update dependency fs-extra to version 6.0.0 (#226)

Tooling:

• Update dependency aws-sdk to version 2.230.1 (#209, #210, #216, #217, #218, #219, #221, #225)
• Update dependency prettier to version 1.12.1 (#211, #214)
• Update dependency mocha to version 5.1.1 (#212, #215)
• Update dependency moment to version 2.22.1 (#213)

v2.2.3

Fixes:

• Decode x-amz-copy-source to support spaces & special characters (#207)

Tooling:

• Update moment (#203)
• Update eslint (#195, #191)
• Update mocha (#197)
• Update aws-sdk (#208, #206, #205, #204, #202, #201, #200, #199, #198, #196, #194, #193, #192, #190)

v2.2.2

Fixes:

• Correctly format XML date (#182)
• Include correct IsTruncated value in listObjects response #187
• Include bucket name in listObjects XML response (Regression) #186
• Include missing size and MD5 in certain event types (Regression) #188

Tooling:

• Use co-mocha for async tests (#177)
• Update aws-sdk (#184)