tag:blogger.com,1999:blog-4126985520350746834.post5934570945027610875..comments2024-03-28T07:00:21.554+00:00Comments on Chris O'Brien: More on optimization, HTTP 304s etc. – a solution?Chris O'Brienhttp://www.blogger.com/profile/10022906552670607366noreply@blogger.comBlogger14125tag:blogger.com,1999:blog-4126985520350746834.post-8885085571291102952009-08-13T10:56:51.567+01:002009-08-13T10:56:51.567+01:00Maxime has now blogged about this here:
http://bl...Maxime has now blogged about this here:<br /><br />http://blogs.msdn.com/maximeb/archive/2009/08/11/blobcache-style-library-and-anonymous-users.aspxAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-31484412515234181262009-07-17T17:45:18.499+01:002009-07-17T17:45:18.499+01:00Thanks for the update.
I hope your environments c...Thanks for the update.<br /><br />I hope your environments continue to behave. I prefer the certainty which would come with storing the files elsewhere but am sure you'll be fine.<br /><br />In terms of the conversation with the MS person - I think this issue has only really hit people's radar recently, so wouldn't necessarily expect every MS person involved with SharePoint to know the issue. <br /><br />Cheers,<br /><br />Chris.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-60513657894157716812009-07-17T15:27:35.893+01:002009-07-17T15:27:35.893+01:00Hi Chris,
Just an update on the FBA site.
So f...Hi Chris, <br /><br />Just an update on the FBA site. <br /><br />So far, despite our initial problems with getting things setup, the cache headers are still coming through just fine on Dev, Sys, and Uat platforms (currently undergoing load testing).<br /><br />We have tested the site for a couple of weeks now, and the only other change we've had to make was to allow all of our FBA users to have restricted read access on the Style Library.<br /><br />So the two main things seem to be: <br />1. Check all the boxes when you clear the cache, and <br />2. Make sure your users have (at least) restricted read access on the Style Library.<br /><br />This seems to mirror your experience with anonymous users.<br /><br />While Maxime indicated that there may be issues with the blobcache, and that it may be best to store the files elsewhere, this is not an option for us this late in the dev cycle. It's a shame she wasn't more specific about the exact nature of the problem.<br /><br />Regardless, when I (and you as it happens) were at the Sharepoint Best Practices Conference, a colleague of mine specifically asked an MS Rep where we should be storing css and their associated images (as opposed to publishing images). We told him it was an FBA authenticated site with various levels of user permissions, and he stated that the Style Library would be the right place to put these. To be fair, caching wasn't mentioned to the MS Rep, but like I say, we are no longer having any issues and it's too late to change anything now...Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-72542593570831822722009-07-06T15:43:54.491+01:002009-07-06T15:43:54.491+01:00Wow, great write-up thanks.
Well done for getting...Wow, great write-up thanks.<br /><br />Well done for getting it working. I can believe that process would work, but am slightly worried something might stop it all working down the line - the flakiness aspect you mention. Be interested to hear how you go over the next few days/weeks.<br /><br />Many thanks for taking the time to write down your workaround!<br /><br />Thanks,<br /><br />Chris.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-91558624611515289332009-07-06T14:35:17.459+01:002009-07-06T14:35:17.459+01:00Just to say that we eventually got the Style Libra...Just to say that we eventually got the Style Library to cache for FBA users! <br /><br />This was the exact order of events for us before it worked (not all steps may be necessary depending on your install):<br /><br />1. Reset the blobcache back to "false" in both web.configs (default zone and internet zone).<br /><br />2. iisreset.<br /><br />3. Manually delete the blobcache directory.<br /><br />4. Set the blobcache to "true" for the internet FBA zone only.<br /><br />5. Go into the internet site as a site collection admin user, go to top level site settings > site collection object cache, select ALL the checkboxes, as per Chris's suggestion.<br /><br />6. iisreset.<br /><br />7. Browse to internet FBA site and it's now working!! (thanks Chris!)<br /><br />8. Go back to the web.config for the default zone and set the blobcache back to "true"<br /><br />A couple of things we found out along the way:<br /><br />i. It's better to get your internet site blobcache working first if you have 2 zones.<br /><br />2. Yslow (a free firefox addon) is a great tool for debugging what is/is not caching (just look at the components tab in the addon window)<br /><br />Needless to say, it does all seem a bit fussy/flakey, and it took us multiple attempts before we got it to work. So to re-state what Maxime said - this "... may or may not temporarily fix this issue."<br /><br />It definitely seemed to us like selecting all the checkboxes made the difference. The "reset disk based cache" checkbox on its own was insufficient.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-80785400365042542372009-07-04T11:10:39.337+01:002009-07-04T11:10:39.337+01:00Interesting. Unfortunately I don't currently h...Interesting. Unfortunately I don't currently have access to a site which uses FBA and images in the Style Library to check. This would mean that it's even more important for static files to be stored outside of the Style Library (and we must <i>test</i> if storing in another library to ensure the problem doesn't occur there also).<br /><br />Thanks for reporting this.<br /><br />Chris.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-59148740377119573492009-07-02T12:33:22.899+01:002009-07-02T12:33:22.899+01:00I am fairly convinced that this bug affects not ju...I am fairly convinced that this bug affects not just anonymous users, but also forms authenticated (membershipprovider) users too.<br /><br />I have tried endless suggestions and fiddles, including the one Chris just posted, but I cannot get the Style Library to cache for forms users.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-61377674466796445172009-07-02T10:19:41.026+01:002009-07-02T10:19:41.026+01:00I am having Style Library caching issues too, but ...I am having Style Library caching issues too, but in my case it is authenticated users NOT anonymous users that are having issues (we do not allow any anonymous access).<br /><br />The interesting thing is that the windows authenticated (default) zone IS caching the Style Library, but the forms authenticated (internet) zone is caching everything EXCEPT the Style Library. (The web.config blobcache directive is exactly the same in both the windows and forms sites).<br /><br />We have looked for most gotchas (e.g. unpublished images won't cache, "Access to the path 'D:\BLOBCACHE\... is denied." in the application event log etc.) but so far no luck. <br /><br />Can anyone confirm if the "known bug" relates only to anonymous users, or whether forms authenticated users are affected too? They seem to be.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-33943403014452872142009-06-14T10:22:46.137+01:002009-06-14T10:22:46.137+01:00@Maxime,
Again, thanks for this. I was having dif...@Maxime,<br /><br />Again, thanks for this. I was having difficulty verifying the test (either way) as per the previous comments, so it's good to get a more solid answer from someone in MS.<br /><br />So we conclude there <i>is</i> a confirmed problem, the proposed solution is unlikely to be reliable, and my earlier post stands that we should look to store CSS/JS files in another library or the filesystem - in line with your recommendation.<br /><br />Cheers!<br /><br />Chris.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-485381691971024682009-06-12T23:45:23.358+01:002009-06-12T23:45:23.358+01:00Flushing the disk based cache (which only does it ...Flushing the disk based cache (which only does it for that zone and server if you use the checkbox) may or may not temporarily fix this issue.<br /><br />as I mentioned in the other post, it's a known bug that isn't currently in plan for fixing with MOSS 2007 (although that can change).<br /><br />I'd deploy CSS/JS/XSL in a different library.<br /><br />MaximeMaxime Bombardierhttp://blogs.msdn.com/maximebnoreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-52080159495127925042009-06-02T08:53:21.244+01:002009-06-02T08:53:21.244+01:00@Will,
Hmm - could be that's what got me. I certa...@Will,<br /><br />Hmm - could be that's what got me. I certainly wasn't aware of this behaviour with Fiddler.<br /><br />Will take the steps you suggest when I get to retesting over the next day or two.<br /><br />Thanks for this, much appreciated!<br /><br />Chris.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-65268064079080261842009-06-01T22:38:29.443+01:002009-06-01T22:38:29.443+01:00I have seen similar behaviour using Fiddler. It se...I have seen similar behaviour using Fiddler. It seems the authentication session is set up between the server and Fiddler. This means that as soon as one session running through Fiddler is authenticated, all sessions are.<br /><br />I believe the way to get around this is the disable connection reuse (Fiddler -> Tools Menu -> General Tab). This means that Fiddler will make an new connection to the server on each request (thus acting more like a real proxy).<br /><br />HTH!<br /><br />WillWillem du Preezhttps://www.blogger.com/profile/01345508305398911663noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-9821507421175067392009-06-01T16:02:47.785+01:002009-06-01T16:02:47.785+01:00@Harold,
Very interesting - I'll do some more tes...@Harold,<br /><br /><I>Very</I> interesting - I'll do some more testing along these lines. One of the aspects which concerned me is that I'm constantly logging in/out to do the tests (all locally on the VM). I might try and get networking sorted to the VM (currently having Windows 7/VMware fun..) so that I can be anonymous on the host but can safely log in on the VM (e.g. to flush BLOB cache).<br /><br />Will also nudge Waldek.<br /><br />Thanks,<br /><br />Chris.Chris O'Brienhttps://www.blogger.com/profile/10022906552670607366noreply@blogger.comtag:blogger.com,1999:blog-4126985520350746834.post-27688014709372052942009-06-01T14:57:50.761+01:002009-06-01T14:57:50.761+01:00Flushing the blobcache didn't solve the issue on m...Flushing the blobcache didn't solve the issue on my VPC. I have a VPC with the default "blueband" publishing site. After flushing the blobcache the max-age is still set to 0. <br /><br />During testing I had some strange behaviour of fiddler though. I used Internet Explorer with an authenticated session and Chrome with an anonymous session. After I did a refresh of the page in Chrome I was suddenly authenticated! <br /><br />Therefore I have used two other techniques to verify the max-age=0 issue. I have installed FireFox with firebug. In the network view of firebug all items in the style library had a max-age of 0. <br />Next I have installed wireshark on the SharePoint VPC to capture the "real" network packages. Then I browsed from my laptop to the site on the VPC with Internet Explorer. And wireshark still showed packeges with max-age=0....<br /><br />Can you please verify that the max-age still isn't 0 when you're anonymous on the site? Or perhaps you were mislead (just as I was) by the strange behaviour of fiddler?<br /><br />Kind regards,<br />HaroldHaroldhttps://www.blogger.com/profile/06064192543150415631noreply@blogger.com