I thought there was a Tag in HTML, something linke
NO-CACHE. Whether the browsers respect it, is another question...
suomi
On 2014-08-08 23:11, Mark jensen wrote:
How to configure Apache to want to forbid browsers from caching all web pages
in www1.example.com/public
and in www1.example.co
On Fri, Aug 8, 2014 at 10:21 AM, Jeff Trawick wrote:
> On Thu, Aug 7, 2014 at 9:45 AM, Agnetta Kamugisha <
> kamugis...@nccommunitycolleges.edu> wrote:
>
>> Jeff,
>>
>> Check this link.
>>
>> We had to implement this workaround.
>> https://www.apachelounge.com/viewtopic.php?t=6037
>
>
> FWIW, AH0
On 8 Aug 2014, at 14:51, Rose, John B wrote:
> We have experimented with using Rewrite to replace /~someuser with /someuser
How very 1997.
> However there is a problem with systems using automounter in the case of an
> http request for a non-existing http://someserver.com/someuser
That's your
How to configure Apache to want to forbid browsers from caching all web pages
in www1.example.com/public
and in www1.example.com/books so every time I ask the browser about any page it
brings it from source.
but I want it to cache the pages under: www1.example.com?
"What's automounter? Is that some process that mounts a user's home directory
on a remote share or something?"
Yes. But only when it is requested. I.e. When you login via ssh, or access a
web site via http whose content is in the remote filesystem, etc. You may refer
to it as autofs.
From: Ri
On 08/07/2014 05:16 PM, M Busche wrote:
Frank,
I don't think you understood what I was trying to say. My complaint
was that in the pre-packaged configuration made with the ubuntu
distribution, the default vhost configuration is placed in a file
prefixed with the string 000 which causes it t
On 08/06/2014 01:18 PM, J.Lance Wilkinson wrote:
Rich Bowen wrote:
On 06/16/2014 11:06 AM, J.Lance Wilkinson wrote:
...snip...
Those of us at edu sites sometimes need to put in for
travel/training
funding as much as a year in advance, and my own institution's
budgeting process c
On 08/08/2014 11:59 AM, Rose, John B wrote:
mod_userdir does not seem to cause superfluous automounter attempts
when an http request to a non-existent web address,
http://website.com/~someuser, is received
Is there some way to implement that mechanism with
http://website.com/someuser http re
mod_userdir does not seem to cause superfluous automounter attempts when an
http request to a non-existent web address, http://website.com/~someuser, is
received
Is there some way to implement that mechanism with http://website.com/someuser
http requests for a nonexistent "someuser"?
From: , J
On Fri, Aug 8, 2014 at 10:56 AM, Rose, John B wrote:
> Looking at the apache.org server-status I do not see any of these …
>
> "OPTIONS * HTTP/1.0"
>
> In the "Request" column
>
> While I see quite a few in ours.
>
> Why does apache.org not have any of these entries?
>
> thanks
>
>
>
You're
Looking at the apache.org server-status I do not see any of these …
"OPTIONS * HTTP/1.0"
In the "Request" column
While I see quite a few in ours.
Why does apache.org not have any of these entries?
thanks
On 08/08/2014 11:21 PM, "Tom Evans" wrote:
>
> On Fri, Aug 8, 2014 at 9:23 AM, Igor Cicimov wrote:
> >
> >> Your .htaccess file:
> >> # ALLOW USER BY IP
> >> order deny,allow
> >> deny from all
> >> SetEnvIF X-Forwarded-For "1.2.3.4" AllowIP
> >> SetEnvIF X-Forwarded-For "5.6.7.8" AllowIP
> >> Al
On Thu, Aug 7, 2014 at 9:45 AM, Agnetta Kamugisha <
kamugis...@nccommunitycolleges.edu> wrote:
> Jeff,
>
> Check this link.
>
> We had to implement this workaround.
> https://www.apachelounge.com/viewtopic.php?t=6037
FWIW, AH00344 after AH00356 shouldn't be interesting. The listening socket
got
We have experimented with using Rewrite to replace /~someuser with /someuser
However there is a problem with systems using automounter in the case of an
http request for a non-existing http://someserver.com/someuser
Anyone have a way to implement the above without doing undesired automount
atte
On Fri, Aug 8, 2014 at 9:23 AM, Igor Cicimov wrote:
>
>> Your .htaccess file:
>> # ALLOW USER BY IP
>> order deny,allow
>> deny from all
>> SetEnvIF X-Forwarded-For "1.2.3.4" AllowIP
>> SetEnvIF X-Forwarded-For "5.6.7.8" AllowIP
>> Allow from env=AllowIP
>> allow from 1.2.3.4
>> allow from 5.6.7.8
> Your .htaccess file:
> # ALLOW USER BY IP
> order deny,allow
> deny from all
> SetEnvIF X-Forwarded-For "1.2.3.4" AllowIP
> SetEnvIF X-Forwarded-For "5.6.7.8" AllowIP
> Allow from env=AllowIP
> allow from 1.2.3.4
> allow from 5.6.7.8source:
http://frustratedtech.com/post/42641261089/htaccess-file
16 matches
Mail list logo
