Details

      Description

      Binary file handling documentation mentions the possibility to use a static server for delivering images and binary files using the following config:

      ezpublish:
          system:
              default:
                  io:
                      url_prefix: "http://static.example.com/"
      

      This actually doesn't work since StreamFileListener only checks semanticPathinfo, not the whole request. Result is 404 errors.

        Issue Links

          Activity

          Show
          Dominika Kurek added a comment - Changes in doc: https://doc.ez.no/pages/diffpagesbyversion.action?pageId=31432023&selectedPageVersions=53&selectedPageVersions=54 and https://doc.ez.no/pages/diffpagesbyversion.action?pageId=25985227&selectedPageVersions=8&selectedPageVersions=9
          Hide
          Bertrand Dunogier added a comment -

          Note that the admin interface won't display images with the URL configured in io.url_prefix

          As far as I can tell, this is partially incorrect. Platform UI will, but the legacy admin will not.

          Show
          Bertrand Dunogier added a comment - Note that the admin interface won't display images with the URL configured in io.url_prefix As far as I can tell, this is partially incorrect. Platform UI will, but the legacy admin will not.
          Hide
          Dominika Kurek added a comment -

          Bertrand Dunogier, thanks, so this warning is not necessary for DEVELOPER at all, as it covers Platform only, not 5.4, so legacy admin does not apply here, right? Fixed, then.

          Show
          Dominika Kurek added a comment - Bertrand Dunogier , thanks, so this warning is not necessary for DEVELOPER at all, as it covers Platform only, not 5.4, so legacy admin does not apply here, right? Fixed, then.
          Hide
          Rui Silva (Inactive) added a comment -

          I have retested this again, on a platform version and on an updated 5.4.
          On the platform installation, everything went ok and all tests for this passed.
          However on a 5.4, as per conclusion on the discussions taken up above, I went to test with creation of an image content via the Public API.
          I followed the example provided on the official documentation, and something strange about the storage paths of the binaries went on, that the rest of QA confirmed as well on their environments. I opened the issue EZP-27245 about this behaviour. It turns out this behaviour is unrelated to the new configurations made available on this jira, but rather about the API itself.
          If there is some other way to test this (image content creation) not through Legacy other than through the public API, on a 5.4, can anyone let me know?
          Ping Bertrand Dunogier, Jérôme Vieilledent.

          Show
          Rui Silva (Inactive) added a comment - I have retested this again, on a platform version and on an updated 5.4. On the platform installation, everything went ok and all tests for this passed. However on a 5.4, as per conclusion on the discussions taken up above, I went to test with creation of an image content via the Public API. I followed the example provided on the official documentation , and something strange about the storage paths of the binaries went on, that the rest of QA confirmed as well on their environments. I opened the issue EZP-27245 about this behaviour. It turns out this behaviour is unrelated to the new configurations made available on this jira, but rather about the API itself. If there is some other way to test this (image content creation) not through Legacy other than through the public API, on a 5.4, can anyone let me know? Ping Bertrand Dunogier , Jérôme Vieilledent .
          Hide
          Rui Silva (Inactive) added a comment -

          Due to lack of feedback, and being unable to properly test this on a 5.4, sanity tests were executed instead, and everything went ok.
          On testing on platform, the PR was tested and everything is ok as well.
          PR tested and approved by QA for 5.4 and platform on master.

          Show
          Rui Silva (Inactive) added a comment - Due to lack of feedback, and being unable to properly test this on a 5.4, sanity tests were executed instead, and everything went ok. On testing on platform, the PR was tested and everything is ok as well. PR tested and approved by QA for 5.4 and platform on master.

            People

            • Assignee:
              Unassigned
              Reporter:
              Jérôme Vieilledent
            • Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: