Re: CommonMiddleware DISALLOWED_USER_AGENTS logic

On Wednesday 24 June 2015 15:15:35 François Schiettecatte wrote: > > Sounds right, but you can do that already with handler403. The change > proposed changes the handling of the user agent to raising > PermissionDenied exception rather than returning a > HttpResponseForbidden(). > That is

Re: 1.9 release planning

For an additional non-core dev data point, I'm also +1 on Loic's 1.10, 1.11, 2.0... plan. Makes it much easier to plan and communicate framework upgrades to clients. On Tuesday, June 23, 2015 at 9:14:25 PM UTC-5, Josh Smeaton wrote: > > I was worried about 1.10 because I wrongly assumed that

Re: CommonMiddleware DISALLOWED_USER_AGENTS logic

Shai Sounds right, but you can do that already with handler403. The change proposed changes the handling of the user agent to raising PermissionDenied exception rather than returning a HttpResponseForbidden(). François > On Jun 24, 2015, at 6:22 AM, Shai Berger wrote: > >

Re: CommonMiddleware DISALLOWED_USER_AGENTS logic

To clarify, I don't object to logging or other custom actions, and it was clear to me that the feature of DISALLOWED_USER_AGENTS already exists; my concern is that the OP's motivation seems to have been to control the design of the error page, which indicates an intention to show it to humans

Re: CommonMiddleware DISALLOWED_USER_AGENTS logic

2015-06-24 1:56 GMT+02:00 Shai Berger : > Could any of the supporters elaborate on the use-case? > Just to clear a possible confusion -- this feature already exists, it was added in 2005 to filter out unwanted crawlers by blacklisting their user-agent. The proposal here is