Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

suspect a race condition sometimes causes "300 gone" #40

Open
GoogleCodeExporter opened this issue Apr 22, 2015 · 2 comments
Open

suspect a race condition sometimes causes "300 gone" #40

GoogleCodeExporter opened this issue Apr 22, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. I do a lot of mod_auth_token "double hit" downloads via a download program
2. always when doing 40 concurrent downloads some of the tokens will expire
3. always some of the tokens do not expire but download wrong file

What is the expected output? What do you see instead?
I expect to see mod_auth_token prepare a x second url that works


What version of the product are you using? On what operating system?
1.0.5

Please provide any additional information below.

it is very hard to replicate, but I had had numerous users mention it on the 
website but I was sceptical, because I had not seen it myself, I have a desktop 
client that hits an authenticated php to get a token via json, that token is 
then the "real" download, when I do a mass download (70 files) it will 
invariably stop randomly and produce a "gone" error in the response. at the 
moment i can't give you this code but I would urge doing a stress test. make 
200 file. give them all unique easily findable name. (EG: 2.test inside is 5000 
number 2 characters" then make a screen scrape routine that will question the 
200 files as tokens then go wget those tokens then write a 3rd routine to check 
that 2.list really has "5000 2's in it" I will write this whole thing and end 
it to you but if you do this you will see that it will fail "gone" about one in 
40 and a similar incidence will be wrong file

Original issue reported on code.google.com by [email protected] on 20 Jul 2014 at 10:03

@GoogleCodeExporter
Copy link
Author

email me conrad dot bate at gmail dot come

Original comment by [email protected] on 20 Jul 2014 at 10:05

@GoogleCodeExporter
Copy link
Author

it is a "410 gone response" not 300

Original comment by [email protected] on 20 Jul 2014 at 10:06

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant