Versions Compared

Old Version 8

changes.mady.by.user Kyle Miller

Saved on

compared with

New Version Current

changes.mady.by.user Kyle Miller

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Improved: A new [gateway] setting, cookieDomains, allows the Content Portal to use the same authentication token across multiple storage domains that share a common base domain. Gateway does this by using the base domain in place of the request's domain for the Set-Cookie response header. (5.2.2: CLOUD-2789)

  • Improved: Gateway has better handling for requests to domains that are marked as belonging to an unknown tenant. These requests are handled as if they are from the "System Tenant" and troubleshooting guidance is recorded in the application logs. (5.2.1: CLOUD-2714)

  • Improved: Gateway has lowered its the default request rewind buffer to 64KB in order to prevent an excessive volume of messages in the storage cluster logs and to match the storage cluster's upper threshold after which 100-continue must be used. This should have no impact for applications using Gateway. (CLOUD-2652)

  • Fixed: A versioned listing now responds in the correct format when the bucket is not versioned, fixing a problem that occurred with Cyberduck 6.2.3 and later. (5.2.2: CLOUD-2796)

  • Fixed: When using a "pam" idsys for Linux users on the Gateway server, requests may slow down after days of high, sustained load. (5.2.1: CLOUD-2727)

  • Fixed: S3 V4 signature errors occurred when using X-Forwarded-Host on a request. Setting [debug] setForwarded=false prevents these errors, if they occur. (5.2.1: CLOUD-2706)

  • Fixed: Multipart/form-data MIME POST uploads that spanned several days of sustained load can result in an OutOfMemoryError. (5.2.1: CLOUD-2732)

  • Fixed: Gateway startup can silently hang if there is a problem communicating with the indexerHosts or if Swarm is not configured with a Search feed. (5.2.1: CLOUD-2419)

  • Fixed: Gateway log warning messages about "Swarm connection failure to node 127.0.0.1" can be generated when using Swarm UI.   (5.2.1: CLOUD-2749)

  • Fixed: Single-shot context creation failed in Gateway 5.1.2 and 5.1.3; the POST failed with a 500 "JSON Validation Errors". (CLOUD-2703)

  • Fixed: In the Content Portal, a collection can appear as a bucket, such that deleting the collection can delete the bucket it was scoped to. For collections erroneously showing the bucket icon, make a small edit and resave them, which causes them to be fully repaired. (CLOUD-2694, CLOUD-2712)

...