Unknown http code 413 about gsb4u

[client9]

Hi, you appear to have a very fragmented set of "chunks" and the request to get new chunks is very large causing the 413 ( request too big ). Have you been running gsb for a long time? or just starting up?

You could just let this run for a day $gsblists = array('googpub-phish-shavar'), then add the other one back in, or zap all the data and start over. I'll have to take a look at what the GSB max request length is (if specified) and adjust the request accordingly.

thanks for the report

nickg

I'm running system about 2 month. And all bases is up to date.

Now I created cron1.sh and cron2.sh and which first is updating goog-malware-shavar and second is updating googpub-phish-shavar. And all bases is up to date, but anyway I cannot run normal cron.sh

I tried to remember my PHP knowledge )

So my sub-list was really fragmented - over 400 ranges.
I change function list2range from
return implode(',', $ranges);
to
return implode(',', array_slice($ranges, 0, 100));

My last fix failed. Somehow chankes didn't process. When I ran update a many times every time the same sub-chunks from goog-malware-shavar processed, but that changes wasnt fixed in database. And because that happend I got very fragmented database. That's how I understand situation.

So I just erase database with erase_database.php and now gsb4u is working excellent.

Thank you for gsb4u. It's great product.