As an aside, if you're using RewriteEngine anyway, you might as well use
repoze.vhm#vhm_path. The X-header stuff is mostly useful if you're using
mod_wsgi. I'm glad we're trying to fix it, though. :)
I know that. This is more natural for anyone to use though--I'm setting up a
client with
Thanks for the feedback on this. I've set up some tests that I
think illustrate what is going on pretty well.
What ends up happening in the current situation is that a url of
/a/b/c/d get chopped off to something like /b/c/d NOT including the
virtual root.
Sorry, where is this happening?
Nathan Van Gheem wrote:
Thanks for the feedback on this. I've set up some tests that I
think illustrate what is going on pretty well.
What ends up happening in the current situation is that a url of
/a/b/c/d get chopped off to something like /b/c/d NOT including the
virtual
like a
simple fix. I've been strapped for time and I'm just trying to do what I
can...
Let me know what you think.
Thanks,
Nathan
On Wed, Dec 30, 2009 at 7:06 AM, Martin Aspeli
optilude+li...@gmail.comoptilude%2bli...@gmail.com
wrote:
Nathan Van Gheem wrote:
Thanks for the feedback
Hello,
I'm having some very odd behavior with using repoze.zope2. The site is being
served using repoze.vhm#vhm_xheaders filter. The correct site is served;
however, it seems that content editors can not see the content actions drop
down menus(Actions, Display, Add new..., etc). More specially,
missing.
I stepped into the code a bit and the plone.contentactions viewlet isn't
even called when repoze.vhm is used.
Thanks,
Nathan
On Sun, Dec 27, 2009 at 9:01 PM, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan Van Gheem wrote:
I'm having
, Dec 27, 2009 at 10:45 PM, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan Van Gheem wrote:
is it possible that it makes an invalid JSON / XML-RPC call when the
virtual hosting is in place? Can you see anything in Firebug about a
failed
misleading in some cases.
So I am in agreement with Malthe on this. I have thought the very same thing
he is talking about here often.
-Nathan Van Gheem
On Tue, Nov 3, 2009 at 12:33 AM, Malthe Borch mbo...@gmail.com wrote:
2009/11/2 Martin Aspeli optilude+li...@gmail.comoptilude%2bli...@gmail.com
Hello everyone,
It seems odd to me that repoze.who would log someone out who is not
authorized to a certain part of a web site. Unless I'm doing something
wrong it seems like there is no good way around it either.
The only solution I could find is creating my own redirecting form plugin
that
...@palladion.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nathan Van Gheem wrote:
Hello everyone,
It seems odd to me that repoze.who would log someone out who is not
authorized to a certain part of a web site. Unless I'm doing something
wrong it seems like there is no good way around
of information (message boards etc.) on how
to proxy from nginx to Pylons apps. Almost all of that should also
apply to bfg.
Hope this helps, would like to hear if you find out anything else.
-- Stephan
Nathan Van Gheem wrote:
Anyone ever deploy repoze.bfg on nginx with mod_wsgi? Right now I'm
Anyone ever deploy repoze.bfg on nginx with mod_wsgi? Right now I'm just
using proxy_pass to the paster serve for repoze.bfg, but it just seems more
natural if this could be done using mod_wsgi.
Any thoughts?
Thanks,
Nathan
___
Repoze-dev mailing list
12 matches
Mail list logo