On Tue, Sep 13, 2011 at 10:00 AM, h3 wrote:
> Most of them were competent developers, but they didn't see the point
> of learning a how to get started with Django because it seemed too
> complicated to setup and use for starters. So they preferred to stay
> in their comfort zone: PHP.
One option
+1 on making the error say more than incorrect username/password. That
is confusing. In regards to leaking information about the user. The
error message in general could be changed to something like this, of
course with better wording:
"Username and password incorrect or access to this page restri
On Tue, Sep 13, 2011 at 12:42 PM, Wim Feijen wrote:
> Hi, thanks for your quick responses!
>
> Flavio, Jan and Florian, it only "gives away information" when an
> attacker guesses both the username and the password right.
I think this is the correct approach. Give them the access warning on
corre
With email you can send and html email and text email in the same
email. You are basically sending and html "alternative" email and part
of a multi-part email.
That would be the best bet.
On Thu, Nov 10, 2011 at 3:03 PM, Ric wrote:
> hi, i receive django email on 500 error.
>
> with that kind of
On Sat, Dec 6, 2008 at 11:54 AM, David Zhou <[EMAIL PROTECTED]> wrote:
>
> On Sat, Dec 6, 2008 at 10:02 AM, Ludvig Ericson
> <[EMAIL PROTECTED]> wrote:
> >
> > On Dec 6, 2008, at 09:07, David Zhou wrote:
> >> Is it possible to reword the introduction on the Django Book website
> >> (http://www.dja
On Fri, May 8, 2009 at 9:42 AM, Marcello Bontempo Salgueiro
wrote:
> Don´t make a core list, put inside the dajngo site
> a new applet for register jobs, like have in the python.org[1]!!
djangogigs.com
On the point of name. I think using the word "contributer(s)" is the
best way to remove confu
