Skip to content
This repository was archived by the owner on Nov 13, 2017. It is now read-only.
This repository was archived by the owner on Nov 13, 2017. It is now read-only.

PATH issue with mod_proxy / mod_rewrite #2

@neoice

Description

@neoice

so as written, theory assumes that it will always operate as its own port with its own root (/). however, if you try and include it as part of another hierarchy, you get PATH-related breakage. for example, I run theory on an internal server and want to access it from an external web server using apache2's mod_rewrite like so:

RewriteRule ^/mpd/(.*) http://192.168.10.1:9099/$1 [P]

now when theory renders, it looks for /js, which may not actually exist. I think this can mostly be fixed by removing the preceding slash from all the paths, replacing it with ./ or defining an internal PATH variable so we can define the root at will. I'd be happy to knock out a patch for you. do you a have a preference on how to do this? or do you even want this? I can just fork and maintain a separate patch for my bizarre edge-case setup :D

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions