Uploaded image for project: 'FOLIO'
  1. FOLIO
  2. FOLIO-897

Avoid external port 9130 in full-stack boxes: folio/stable, folio/testing

    XMLWordPrintable

    Details

    • Template:
    • Development Team:
      Core: Platform

      Description

      Change the full-stack boxes folio/stable and folio/testing so that they can be run on a single host and on the single standard port 80 (or 443 when using https).

      Several libraries have strict firewall settings where ports like 9130 are blocked. To make demoing and testing FOLIO as easy as possible the full-stack boxes should come with a default installation with front end and back end on the same port (80 or 443). (The option to configure other hostnames and ports can still remain.)

      Having frontend and backend on the same hostname and port has the additional benefit that the browser doesn't send any Cross-Origin Resource Sharing (CORS) preflight requests; there may be some locations where this significantly reduces the latency.

        TestRail: Results

          Attachments

            Issue Links

            blocks

            Umbrella - FOLIO-1134 Secure public AWS instances

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open
            is duplicated by

            Task - A task that needs to be done. FOLIO-1849 Proxy Okapi through standard HTTP/HTTPS ports for hosted folio-snapshot and folio-testing

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            relates to

            Task - A task that needs to be done. OKAPI-653 Document that X-Okapi-Url may end with a path like https://folio.example.com/okapi

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests RMB-244 OkapiUrl with path in ConfigurationsClient

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. RMB-247 OkapiUrl with scheme and path in HttpModuleClient* HttpClient*

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            Task - A task that needs to be done. STCOR-29 Re-organise the webpack configuration

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Sub-task - The sub-task of the issue STRIPES-177 Investigate pre-flight OPTIONS calls before each Okapi call

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

              Activity

                People

                Assignee:
                floriangleixner Florian Gleixner
                Reporter:
                julianladisch Julian Ladisch
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases