Version 6x release notes

June 25, 2014 - February 19, 2015

 

 


Release 6.2.2.0 (01/22/2015: New Filters: Add Header, Forwarded Protocol, IRI Validator)

Key Summary T Assignee P Status story points
Loading...
Refresh

New Features

  1. The Add Header filter. See: Add Header Filter. REP-729 - Getting issue details... STATUS
  2. The Forwarded Protocol filter. See: Forwarded Protocol Filter. REP-1527 - Getting issue details... STATUS
  3. The IRI Validator filter. See: IRI Validation filter REP-1595 - Getting issue details... STATUS

Enhancements

  1. The timeout for the Akka client's future is now dynamic and based on the configured HTTP Socket Timeout. REP-1540 - Getting issue details... STATUS
  2. Optional quality for X-Tenant-Id and X-Project-Id to indicate default.  REP-1560 - Getting issue details... STATUS

Bug Fixes

  1. Rate limits for a user are no longer reset based on the shortest duration limit.  REP-1528 - Getting issue details... STATUS

Known Issues

  1. Rate limiting data may be corrupted if multiple limits share the same limit ID value. To avoid this issue, all group IDs and limit IDs should be unique. See  REP-2233 - Getting issue details... STATUS

Release 6.2.1.2 (01/09/2015: Rate Limit Bug Fix)

Key Summary T Assignee P Status story points
Loading...
Refresh

Known Issues

  1. Rate limiting data may be corrupted if multiple limits share the same limit ID value. To avoid this issue, all group IDs and limit IDs should be unique. See  REP-2233 - Getting issue details... STATUS

Release 6.2.1.0 (12/15/14: Content Type Stripper Filter)

Key Summary T Assignee P Status story points
Loading...
Refresh

New Features

  1. New filter will strip the content type on a GET request if the body is empty or contains nothing but line space characters for the configured number of characters.  REP-1301 - Getting issue details... STATUS
  2. Known Issues

    1. Rate limiting data may be corrupted if multiple limits share the same limit ID value. To avoid this issue, all group IDs and limit IDs should be unique. See  REP-2233 - Getting issue details... STATUS

Release 6.2.0.3 (11/12/2014: RPM package correction on spurious error)

  • Simply correction to RPMs.  No new features/bug fixes.

    Known Issues

    1. Rate limiting data may be corrupted if multiple limits share the same limit ID value. To avoid this issue, all group IDs and limit IDs should be unique. See  REP-2233 - Getting issue details... STATUS

Release 6.2.0.2 (11/07/2014: Translation improvements, Auth Z fix, deprecate Utility Grid artifacts, Packaging Changes)

Key Summary T Assignee P Status story points
Loading...
Refresh

Breaking Changes

  1. Renamed all Java packages to org.openrepose.*. Refer to the story for more details.  REP-286 - Getting issue details... STATUS
  2. Utility Grid artifacts (ug-repose-filters, ug-repose-valve) are no longer available.  REP-710 - Getting issue details... STATUS
  3. Installation packages were updated to correct permissions and improve consistency between packages.  REP-1148 - Getting issue details... STATUS
    1. The repose-filters RPM package is now repose-filter-bundle.
    2. The repose-extension-filters RPM package is now repose-extensions-filter-bundle. 

Enhancements

  1. Changed the ownership, permission, and location of many files and directory installed by Repose packages. Note that the behavior of Repose packages can now be found at: Package Contents - Archived REP-1148 - Getting issue details... STATUS
  2. Restricted dependencies between Repose packages to the same version.  REP-1120 - Getting issue details... STATUS
  3. Client Authorization filter now supports a role tag as well as ignore-tenant-role tag within ignore-tenant-roles to be more consistent with client authentication filter. REP-963 - Getting issue details... STATUS

Known Issues

  1. Rate limiting data may be corrupted if multiple limits share the same limit ID value. To avoid this issue, all group IDs and limit IDs should be unique. See  REP-2233 - Getting issue details... STATUS

Release 6.1.1.1 (10/09/2014: OpenStack v3 Identity enhancements, Rackspace Basic Auth filter, Logging updates)

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Loading...
Refresh

New features

  1. OpenStack Identity v3: Allow for validation of project-id in URI against project-id(s) in token.  REP-894 - Getting issue details... STATUS
  2. OpenStack Identity v3: X-Default-Region header is populated if available  REP-1001 - Getting issue details... STATUS
  3. OpenStack Identity v3: Option to send all available project Ids as multiple X-Project-Id headers  REP-900 - Getting issue details... STATUS
  4. OpenStack Identity v3: X-Impersonator-Id and X-Impersonator-Name headers are populated if impersonation information is available REP-928 - Getting issue details... STATUS
  5. Rackspace Basic Auth Filter: Allow for Authentication using a User Name and API key via the standard HTTP Basic Auth mechanism.  REP-382 - Getting issue details... STATUS
     

Enhancements

  1. Replaced a custom built static sized pool with an Apache Commons pool that dynamically sizes.  REP-1060 - Getting issue details... STATUS

Bug Fixes

  1. Leaving out the <request-endpoint> element in the rate-limiting config no longer causes a NullPointer exception.  REP-1048 - Getting issue details... STATUS
  2. The getContentType method in the MutableHttpServletRequest/Response classes now reflects changes to the header, and does not return a list.  REP-1152 - Getting issue details... STATUS

Known Issues

  1. Rate limiting data may be corrupted if multiple limits share the same limit ID value. To avoid this issue, all group IDs and limit IDs should be unique. See  REP-2233 - Getting issue details... STATUS

Release 6.1.0.3 (Global Rate Limits, OpenStack Identity V3 Auth)

Key Summary T Assignee P Status story points
Loading...
Refresh

Potential incompatibilities:

  1. Repose no longer uses a listener port to trigger shutdown; instead, a JVM shutdown hook is called when the process is signaled to terminate.  REP-306 - Getting issue details... STATUS

New features

  1. OpenStack Identity V3 is supported.  REP-819 - Getting issue details... STATUS
  2. Licenses have been placed in same path structure for both RPM's and DEB's.  REP-702 - Getting issue details... STATUS
  3. Rate Limiting supports matching against query parameter keys.  REP-480 - Getting issue details... STATUS
  4. Rate Limiting supports global rate limits.  REP-667 - Getting issue details... STATUS

Bug fixes

  1. Rate Limiting doesn't take percent-encoded paths into account.  REP-699 - Getting issue details... STATUS
  2. Services listed in the system model now get validated.  REP-77 - Getting issue details... STATUS
  3. Repose now enforces that one and only one default endpoint destination must be explicitly identified if there is more than one endpoint configured.  REP-763 - Getting issue details... STATUS
  4. Repose now correctly performs tenant ID check in the Client Auth Filter when the tenant ID is not the default tenant ID.  REP-892 - Getting issue details... STATUS
  5. Response Messaging Service was removing newlines from file templates.
  6. Repose will now validate the uri it receives before doing any of the filter chain. If the uri is invalid repose returns a 400 to the user instead of the 500s that we were potentially seeing before.  REP-997 - Getting issue details... STATUS

Enhancements

  1. Removed checks for redundant configs.  REP-745 - Getting issue details... STATUS

Known Issues

  1. Rate limiting data may be corrupted if multiple limits share the same limit ID value. To avoid this issue, all group IDs and limit IDs should be unique. See  REP-2233 - Getting issue details... STATUS

Release 6.0.2 (6/25/2014: Java 1.7)

Key Summary T P Status Assignee
Loading...
Refresh

Breaking changes

  1. Repose is now built and released on Java 1.7. This enables us to use Jetty 9, which resolves  REP-370 - Getting issue details... STATUS . Users running on Java 1.6 must upgrade.
  2. Repose now uses Jetty 9 for both the valve deployment as well as the distributed datastore. Side effects of this change include:
    1. The value of the  content-type header is now normalized to be all lower-case.
    2. The size of the value for all headers is allowed to be larger.
    3. Headers with a null value or empty value are stripped.
  3. We have removed the Replicated Datastore, as it was deprecated.  REP-506 - Getting issue details... STATUS
  4. We have removed the HTTP Logging Filter, as it was deprecated. Use the SLF4J HTTP Logging filter instead.  REP-327 - Getting issue details... STATUS

New features

  1. The API Validator Filter can now create graphs of the application states of your API.  REP-323 - Getting issue details... STATUS
    1. For Example: 
  2. Licenses have been reviewed and detailed in License. License files added to the code base.  REP-269 - Getting issue details... STATUS REP-18 - Getting issue details... STATUS

Bug fixes

  1. Compression Filter should remove "Accept Encoding" heading upon decompression.  REP-110 - Getting issue details... STATUS
  2. Distributed Datastore is now closing long running connections rather than delaying them in FIN_WAIT.  REP-370 - Getting issue details... STATUS
    1. Ran test for 6 hours and 15 minutes.  Test was to execute 10 requests every 20 seconds.  No irregular behavior was seen.  We went from utilizing 768 file handlers in the beginning of the test to 832 file handlers in the end of the test.  The test mimicked what our client saw in production as far as load distribution; however, the issue went away.

Known Issues

  1. Rate limiting data may be corrupted if multiple limits share the same limit ID value. To avoid this issue, all group IDs and limit IDs should be unique. See  REP-2233 - Getting issue details... STATUS