[pLog-svn] Htaccess update
Oscar Renalias
oscar at renalias.net
Wed Feb 28 17:36:41 EST 2007
If you were getting errors, check your Apache error logs and have a
look at the URLs that were causing those 40x errors. In lifetype.net
I noticed that repeated requests for favicon.ico were causing those
errors, you may be having the same problem. And with regards to using
subdomains and eliminating /blog/ or /blog.php/ from the URL, as Jon
said it won't cause any problem as long as you keep /post/, /
archives/, /resource/, etc.
On 1 Mar 2007, at 00:05, Jon Daley wrote:
> Please give an example when error.php would be used? It isn't
> used on any blog that I know about. There is only one blog that I
> used aa
> similar sort of rule to yours, although LT wasn't the only thing on
> that
> site, so my rule was more complicated. But, for "normal"
> installations,
> those rules aren't needed - nor is error.php. That is only for
> errors.
>
> On Wed, 28 Feb 2007, Ayalon wrote:
>> SO you think for performance reasons it's better to let it be
>> handled with
>> the error.php instead of a rewrite rule?
>>
>> -----Oorspronkelijk bericht-----
>> Van: plog-svn-bounces at devel.lifetype.net
>> [mailto:plog-svn-bounces at devel.lifetype.net] Namens Jon Daley
>> Verzonden: woensdag 28 februari 2007 21:52
>> Aan: plog-svn at devel.lifetype.net
>> Onderwerp: Re: [pLog-svn] Htaccess update
>>
>> The only reason one would need the sort of thing you are talking
>> about is to have urls that don't have /post, /archive, /category,
>> etc in
>> them. For example, http://jon.limedaley.com uses the default
>> rules. And
>> the /plog is there because lifetype is installed in the /plog
>> directory,
>> as opposed to the rest of my site.
>> You don't need /blog.php or /blog in your URLs, with or without
>> your htaccess rules.
>> The current "complicated" htaccess rules are only for modrewrite
>> URLs. I guess you could get rid of the ForceType/SetHandler lines
>> at the
>> expense of using your rewrite rule for every access. How much
>> time do
>> your two rewrite rules take? I assume it is a small, and fairly
>> unnoticeable delay, but it does add a check to see if the file
>> exists for
>> every HTTP request, and so at least for large sites, might not be
>> ideal.
>>
>>
>> On Wed, 28 Feb 2007, ayalon at blog.nl wrote:
>>> Well it's search engine friendly, but there are called custom
>>> url's that's
>>> right.
>>>
>>> Anyway lifetype will need the error php in the errorducoment for
>>> this to
>> work
>>> correctly if you don't want /blog.php or /blog in your url. And
>>> this will
>>> create error logs (look at the wiki pages).
>>>
>>> With my solution this is not happening anymore. And as far as i
>>> can see
>>> a lot of
>>> lifetype admins are using this.
>>>
>>> Citeren Oscar Renalias <oscar at renalias.net>:
>>>
>>>> If you were getting errors in your log files it's beacause you had
>>>> something wrong in the first place. When using subdomains or custom
>>>> URLs, you should not be getting any 40x errors at all and if you
>>>> did,
>>>> you should have removed the ErrorDocument parameters from
>>>> your .htaccess and then see what was failing. Otherwise
>>>> error.php is
>>>> only needed for the so-called "search engine friendly" URLs.
>>>>
>>>> On 28 Feb 2007, at 17:43, Ayalon wrote:
>>>>
>>>>> Hi All,
>>>>>
>>>>> As also posted on the forums:
>>>>> http://forums.lifetype.net/viewtopic.php?p=33349
>>>>>
>>>>> To keep errors out of the logfiles and to handle all the requested
>>>>> by the
>>>>> server not by having errors in the logfiles when using
>>>>> subdomains and
>>>>> friendly url's
>>>>>
>>>>> The only thing I have in my .htaccess is the following:
>>>>>
>>>>> RewriteEngine On
>>>>> RewriteBase /
>>>>>
>>>>> RewriteCond %{REQUEST_FILENAME} !-f
>>>>> RewriteCond %{REQUEST_FILENAME} !-d
>>>>> RewriteRule . /blog.php
>>>>>
>>>>> This will do the job for almost everything, except the pager. This
>>>>> is not
>>>>> working via this solution, probably because it's not handled the
>>>>> same way as
>>>>> the posts and the categories are.
>>>>>
>>>>> Anybody has an idea on this? If this works fine, we don't even
>>>>> need
>>>>> the huge
>>>>> htaccess file anymore within lifetype and it will handle
>>>>> everything
>>>>> a lot
>>>>> faster inside the environment as it doesn't have to pass the
>>>>> error.php
>>>>> before finding the good file.
>>>>>
>>>>> What do you guys think?
>>>>>
>>>>> Regards,
>>>>> Ayalon
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> pLog-svn mailing list
>>>>> pLog-svn at devel.lifetype.net
>>>>> http://limedaley.com/mailman/listinfo/plog-svn
>>>>>
>>>>
>>>> _______________________________________________
>>>> pLog-svn mailing list
>>>> pLog-svn at devel.lifetype.net
>>>> http://limedaley.com/mailman/listinfo/plog-svn
>>>>
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> pLog-svn mailing list
>>> pLog-svn at devel.lifetype.net
>>> http://limedaley.com/mailman/listinfo/plog-svn
>>>
>>
>> --
>> Jon Daley
>> http://jon.limedaley.com/
>>
>> If you think good architecture is expensive, try bad architecture
>> -- Brian Foote and Joseph Yoder
>> _______________________________________________
>> pLog-svn mailing list
>> pLog-svn at devel.lifetype.net
>> http://limedaley.com/mailman/listinfo/plog-svn
>>
>>
>> _______________________________________________
>> pLog-svn mailing list
>> pLog-svn at devel.lifetype.net
>> http://limedaley.com/mailman/listinfo/plog-svn
>>
>
> --
> Jon Daley
> http://jon.limedaley.com/
>
> Keep a stiff upper chin.
> -- Sam Goldwyn, Hollywood producer
> _______________________________________________
> pLog-svn mailing list
> pLog-svn at devel.lifetype.net
> http://limedaley.com/mailman/listinfo/plog-svn
>
More information about the pLog-svn
mailing list