Issue #720 resolved

tricky base problem when mixing tools.proxy and tools.caching

guest avatarguest created an issue

in face this may be a "base" problem, at __init__.py

def url(path="", qs="", script_name=None, base=None, relative=False):
    ...
        if base is None:
            base = request.base
        ...
    else:
        # No request.app (we're being called outside a request).
        # We'll have to guess the base from server.* attributes.
        # This will produce very different results from the above
        # if you're using vhosts or tools.proxy.
        if base is None:
            base = server.base()

there is a problem already known if we use tools.proxy,

tools.proxy have a 'base' variable, the "request.base" will be rewritten by tools.proxy,

even the "base" variable doesn't set up,

this "base = server.base()" will result a different url between request/respond if we using tools.proxy,

then caching utility can't get cached content because it use "cherrypy.url"

Comments (4)

  1. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.