Regardless, your solution is not a good one, because you shifted from a
password hashing algorithm that enables protection against brute-force
attacks to a different algorithm with no similar protection.
I would highly suggest you read
But that's all I revised of the code. The configuration file of server
engine and all the other things keep the same.
On Tuesday, November 21, 2017 at 2:09:08 PM UTC-5, Jason wrote:
>
> That is not a good solution. There's a reason why the default password
> hashing algorithm is complex.
>
>
That is not a good solution. There's a reason why the default password
hashing algorithm is complex.
And I find it hard to believe that a password hash is the culprit here.
Maybe a quarter second or so added to a response, but 10 seconds? that's
definitely not the cause.
--
You received
Hi Jason,
Thanks for your help! I just solved the bug.
The reason of the bug is that in the first step after I verify the worker's
identification, I should put them in the database. And in django default
setting, PASSWORD_HASHERS is set to PBKDF2 to hash the password for each
worker. It is a
Does that worker call execute slowly each time you call it? Or is it just
the once?
I'd copy that URL and try calling it several times with an REST API client
like Postman. Does the request execute that slowly each time you call it,
or is it just the initial call that is slow?
--
You
Hi,
The worker id and hit id are passed via GET. (It's a website for amazon
mechanical turker to finish tasks.) And views.py checked their worker id
and hit id to see whether they are valid. If they're valid, then the turker
will be directed to the following pages.
On Sunday, November 19,
Hello,
How does the verification work?
Regards,
Antonis
Antonis Christofides
http://djangodeployment.com
On 2017-11-19 02:38, flora.xiaoyun.hu...@gmail.com wrote:
> Thank you for your reply. The first page always loads slowly while the rest of
> the pages loads at a normal speed. Whether I
And this is the first few lines of requests in the network section in
developer tools. You can see that the first step to verify the user's
identification takes so long.
Thank you for your reply. The first page always loads slowly while the rest
of the pages loads at a normal speed. Whether I restart the apache or not
doesn't affect the speed of loading the first page - always slow.
Below is the configuration file in the sites-available folder under apache.
My
I would suggest you post the configuration file here as well as the server
specifications and average CPU/memory usage. Because what you're
describing is definitely not normal and is most likely related to how
Apache is configured.
A point of clarification: does the first page always load
10 matches
Mail list logo
