+972 52-548-6969
What is up with all those 404?
time to read 1 min | 54 words
Recently I had a spate of posts showing up, and then reporting 404. The actual reason behind that was that the server and the database disagreed with one another with regards to the timezone of the post (one was using UTC, the other local). Sorry for the trouble, and this shouldn’t happen any longer.
Comments
That makes sense. I just thought I was following a super secret Ayende on twitter and getting all your posts from the future. :P
This post is also showing up as a future post.
I suspected it was related to timezones, because the posts eventually became accessible after a certain time... glad you fixed it!
Not sure if it would have helped here, but FWIW I love using DateTimeOffset (added in 3.5 / SQL 2008) for reasons like this. Finally I don't have to worry about keeping everything UTC everywhere.
As Ferris would say: It is so choice. If you have the means, I highly recommend using it.
.NET side: http://msdn.microsoft.com/en-us/library/system.datetimeoffset.aspx
SQL side: http://msdn.microsoft.com/en-us/library/bb630289.aspx
I which we all could move to Zulu time (UTC) with no daylight saving. Imagine the global savings on software development!
Tags links on the right do not seem to work
This problem still exists.
Right now it is 11:38 AM GMT on 4 Jan 2012. In Google Reader a post appears titled "Embracing RavenDB" at http://ayende.com/blog/152707/embracing-ravendb
Google Reader displays:
Received: Jan 4, 2012 10:43 AM Published: Jan 4, 2012 10:00 AM
What's strange is that the post does not appear in your RSS feed anymore (view-source:http://ayende.com/blog/rss). It is as if the post was published long enough for Google Reader to pick it up, but then retracted.
Here is what your RSS feed looks like at 11:44 AM GMT:
https://gist.github.com/1559702
Why is Google Reader showing a post "published" at 10:43 AM that doesn't appear in your feed at 11:44 AM?
In any case, clicking on the post title in Google Reader displays a 404.
Paul
Paul, Yes, but that stems from a different issue. I moved the post from time to time, but it didn't got moved correctly because of a different problem. Working on it now.
Comment preview