I've read the
article for the Fetchsize config option. This is my first experience with Wiki software, so this is all new to me.
Fetchsize Article Text Excerpt wrote
external servers won't be hammered (local caching instead of hotlinking)
1) How does local caching compare to using the media manager? Both are locally served, but are there any problems with local caching that make it less desirable than taking the extra time to use the media manager?
2) With the media manager, I can browse images and find them easily. But can I even view locally cached images inside the wiki (browsing like you can with media manager), or will I have to delve into my FTP and sift through directories to locate them?
3) I set a Fetchsize limit way above my test image file size. Then I refreshed the page but it is still linking to the internet version. So, is that test image now locally cached or do I need to take an additional step to ensure it is locally cached?
4) Once cached, is there anyway to know that the image is being served from the local cache, versus the originating internet URL the link tooltip reports? My current image link is the URL link is enclosed in double braces {{image url}}.
Fetchsize Article Text Excerpt wroteit allows for nicely resized external images
5) In what manner does this resizing work? I didn't see anything in the Fetch article about it or any resize options on the admin Configuration Settings page.
Fetchsize Article Text Excerpt wrotethis could be used for denial of service attacks... It is recommended to enable the option with smaller (common image) sizes, like 100 to 150kb.
6) My wiki will be closed to the public, yet still hosted on the internet. Am I still at risk for a DOS attack? I ask because I'm trying to figure out what a good size for Fetchsize would be. While large file size images are uncommon, I'd still like to allow as much to be locally cached as possible. Seems it would be faster than always accessing external URL's, not to mention kinder.
7) Can setting a large Fetchsize limit, beyond the DOS attack possibility, have any other undesirable effects? I was thinking something like 50MB just to make sure everything gets cached.