Open GoogleCodeExporter opened 9 years ago
There are 2 ways of dealing with this:
1)
- create a subfolder where to store codes temporarily
- each code is generated and saved with unique name indicating it's contents.
perhaps based on a MD5 of the contents?
- these entries should be cleaned-up periodically, as it is a potential DoS
source.
Or the script, on each run, should do the clean-up, by deleting any generated
files, olders first, so that only a number of $cnt_qr_code files exist at any
one time.
2) the actual qr code generation be live, and the IMG tag in the page call this
script, which returns the contents of the QR code image.
This can increase CPU load on the server and be another type of DoS if not
implemented properly. Perhaps locking?
Original comment by andrixnet
on 1 Apr 2014 at 2:54
Issue 66 has been merged into this issue.
Original comment by wloczynutka
on 11 Apr 2014 at 9:25
The QR code page features a possibly hardcoded example URL
http://opencaching.pl/viewcache.php?wp=OP3C90
The example URL should be generated from $absolute_server_URI.
The image is a sample label with hardcoded opencaching.pl text as pixels.
The image template used for generating this label should follow a similar
structure as statpics, that is have several label images available and user
select which one to use. Among others, I'd like to have a pure QR code image,
no fancy anything around it.
Also, a link could be added to cache listing page to generate a qr code with
one click, rather then copy paste the URL.
Original comment by wloczynutka
on 11 Apr 2014 at 9:25
Hardcoded links are solved. Every node can make his own link or image via
settings.inc.php.
Example is in settingsDefault.inc.php.
Original comment by henricus...@gmail.com
on 3 Dec 2014 at 6:29
Original issue reported on code.google.com by
boguslaw...@gmail.com
on 17 Feb 2014 at 12:38