Roy T. Fielding wrote:
I ended up fixing all website generation to utf-8 -- I am surprised
that it lasted this long with just iso-8859-1.
Thanks -- looks good!
Yes, that is what I prefer as well. All paperwork is done, so please
let us know when you have an export. I (or one of the other
RewriteCond ${REMOTE_USER} . does not seem to work when the REMOTE_USER is
not defined. The statement evaluates to true.
I plan of writing -e directive.
Michele
-Original Message-
From: Bob Ionescu [mailto:bobsie...@googlemail.com]
Sent: Monday, February 09, 2009 8:34 AM
To: modules-..
I'd double check and triple check -
something undefined can't match anything.
What is the EXACT code you're using?
Also, rewrite has -f to check to see if
it's a file, and -d for a directory, just
like the standard "test" command, Perl,
and other common tools. These common
tools use -e to t
On Thu, Feb 12, 2009 at 2:25 PM, Michele Waldman wrote:
> RewriteCond ${REMOTE_USER} . does not seem to work when the REMOTE_USER is
> not defined. The statement evaluates to true.
What happens when you use the proper syntax, %{REMOTE_USER}?
--
Eric Covener
cove...@gmail.com
Hello All,
I am trying to setup Apache 2.2.9 as a transparent proxy. So that the
users don't have to configure their browsers. Now the URLs coming in
are relative for transparent proxy, so normally apache tries to look
it up on the filesystem and it obviously fails. So I added a
RewriteRule to con
I've never used Apache as a transparent proxy I've always used squid.
On Thu, Feb 12, 2009 at 7:50 PM, Pranav Desai wrote:
> Hello All,
>
> I am trying to setup Apache 2.2.9 as a transparent proxy. So that the
> users don't have to configure their browsers. Now the URLs coming in
> are relative f
