26. September 2008 08:34
The other day, I subscribed this blog to FeedBurner . This was all meant to be the way forward . What i was trying to do was to use a Web Request to someone's feed url (in my example, http://feeds.feedburner.com/aboobolaky) to gather a few blog entries from the feed (a bit like the blog roll on the left hand side!).
It turns out that the web request fails with a status of "ProtocolError" , with an Exception of "The remote server returned an error: (404) Not Found." . However, if you use an RSS Reader or even point your web browser to the link, it works just fine!!
Question here..How do we isolate the problem?
- Is this intentional?
- Is a proxy server responsible for this?
- Or, maybe it has something to do with the User Agent?
I'll be thinking about this and post an update sooner or later.
In the meantime, I'd better revert my feed url to how it was before
public partial class _Default : System.Web.UI.Page
public class RequestState
// This class stores the State of the request.
const int BUFFER_SIZE = 1024;
public StringBuilder requestData;
public byte BufferRead;
public HttpWebRequest Request;
public HttpWebResponse response;
public Stream streamResponse;
BufferRead = new byte[BUFFER_SIZE];
requestData = new StringBuilder();
Request = null;
streamResponse = null;
protected void Page_Load(object sender, EventArgs e)
HttpWebRequest httpRequest = (HttpWebRequest)WebRequest.Create("http://feeds.feedburner.com/aboobolaky");
RequestState myRequestState = new RequestState();
myRequestState.Request = httpRequest;
private static void ProcessResponse(IAsyncResult async)
RequestState state = (RequestState)async.AsyncState;
using (HttpWebResponse response = (HttpWebResponse)state.Request.EndGetResponse(async))
XmlDocument doc = new XmlDocument();
XmlNodeList nodes = doc.SelectNodes("rss/channel/item");
foreach (XmlNode node in nodes)
string title = node.SelectSingleNode("title").InnerText;
/*likewise,list the relevant nodes under /rss/channel/item..*/
catch (System.Net.WebException ex)
9. September 2008 07:55
Yesterday, I took the courage to format my laptop and install a brand new Windows XP. After having spent hours in finding my notebook drivers, I decided to go ahead with it and trashed all my existing partitions and re-created new ones (I must have loved this because its been such a long time..:P ).
HOURS Later (yes..its an old laptop), I launched windows update. Win XP SP3 came up as a priority and therefore I installed it..After having rebooted the machine, I re-lauched WU to install the other updates(the most important update for me was IE7)..Once the download updates were complete, all the subsequent installations failed!!! Of course, there wasn't any log as to why the updates failed to install!!
It turns out that I did not reboot my machine after having installed the Windows Update Agent (RECALL: this is the first step prior to downloading updates from WU). Since SP3 was installed straight after the installation of WU Agent, some dlls were not properly registered and that caused updates to fail. KB943144 goes into a bit more detail and provides resolutions to this problem
Oh what a life...