Details

    • Release Notes Text:
      Hide
      Users can now access local workspace files using the embedded LiveReload proxy (thus, using http:// protocol instead of file:// protocol). The benefit of this solution is that the LiveReload proxy automatically injects the livereload.js script at the bottom the the returned HTML pages. This means that the user does not have to install and enable the livereload extension in her browsers.
      Show
      Users can now access local workspace files using the embedded LiveReload proxy (thus, using http:// protocol instead of file:// protocol). The benefit of this solution is that the LiveReload proxy automatically injects the livereload.js script at the bottom the the returned HTML pages. This means that the user does not have to install and enable the livereload extension in her browsers.

      Description

      In 4.1.0.Alpha2, static files can be accessed from the local browser using the file:// scheme.
      These files could also be accessed from the embedded web server (see if the default 35729 port can be reused), so that static files can be accessed by remote devices. In that case, the livereload script could be automatically injected at the bottom of html pages.

      This proxy only allows for access to files in the workspace, it MUST NOT let some browser access files out of the workspace.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  xcoulon Xavier Coulon
                  Reporter:
                  xcoulon Xavier Coulon
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: