Casting of responseHeaders max age config causing error during migration

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Won't Do
    • Priority: L3 - Default
    • 3.9.6, 3.10.6
    • Affects Version/s: 3.10.0, 3.10.1, 3.9.5, 3.10.2, 3.10.3, 3.10.4, 3.10.5
    • Component/s: backend, documentation
    • Not defined

      – After further evaluating this ticket may not be required. To be further clarified –
      See slack linked in comment for more context.

       

      Context:

      In the linked support ticket, the customer is unable to upgrade to 3.9.5 due to an error relating to the casting of the ResponseHeaders max.age configuration. This was introduced with OPT-6724.

       

      AT:

      • the change in casting of max.age in ResponseHeadersConfiguration introduced with OPT-6724 is reverted

       

      Testing Notes:

      Follow steps to reproduce from support ticket and confirm max.age casting error does not occur. 

            Assignee:
            Unassigned
            Reporter:
            Helene Waechtler
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: