<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>robbie &#187; site</title>
	<atom:link href="http://www.wellitworkedlasttime.com/robbie/index.php/category/site/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wellitworkedlasttime.com/robbie</link>
	<description>wellitworkedlasttime.com</description>
	<lastBuildDate>Wed, 04 Nov 2009 22:08:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>ǝlƃooƃ noʎ ʞɔnɟ</title>
		<link>http://www.wellitworkedlasttime.com/robbie/index.php/2008/google-trends-hacked/</link>
		<comments>http://www.wellitworkedlasttime.com/robbie/index.php/2008/google-trends-hacked/#comments</comments>
		<pubDate>Sun, 13 Jul 2008 18:51:41 +0000</pubDate>
		<dc:creator>robbie</dc:creator>
				<category><![CDATA[security]]></category>
		<category><![CDATA[site]]></category>

		<guid isPermaLink="false">http://www.wellitworkedlasttime.com/robbie/?p=45</guid>
		<description><![CDATA[Admittedly 5 hours behind the curve on this one, but I just randomly stumbled on this on google trends. looks like someone&#8217;s got a new googlehack on the go - in the form of the clever upside down ǝlƃooƃ noʎ ʞɔnɟ. what is interesting is that this term doesn&#8217;t seem to have existed prior to today, so to [...]]]></description>
			<content:encoded><![CDATA[<p>Admittedly 5 hours behind the curve on this one, but I just randomly stumbled on this on <a href="http://trends.google.com/trends?hl=en" title="Google Trends">google trends</a>. looks like someone&#8217;s got a new googlehack on the go - in the form of the clever <a href="http://www.revfad.com/flip.html" title="flip">upside down</a> <a href="http://www.google.co.uk/search?hl=en&amp;safe=off&amp;q=%C7%9Dl%C6%83oo%C6%83+no%CA%8E+%CA%9E%C9%94n%C9%9F&amp;btnG=Search&amp;meta=" title="ǝlƃooƃ noʎ ʞɔnɟ">ǝlƃooƃ noʎ ʞɔnɟ</a>. what is interesting is that this <a href="http://www.google.com/trends?q=%C7%9Dl%C6%83oo%C6%83+no%CA%8E+%CA%9E%C9%94n%C9%9F" title="ǝlƃooƃ noʎ ʞɔnɟ">term</a> doesn&#8217;t seem to have existed prior to today, so to get it into the top search spot in just a few hours is significant. a deliberate mass google search? would need an impressive bot-network to pull off the millions of hits required though (or a viral network of lots of people with time on their hands). perhaps a google trends vulnerability then? hmm. either way, having hit the top spot &#8211; i&#8217;d now expect blogs to punt the search frequency back up after this initial spike. which is perhaps the real hack&#8230;</p>
<p><img src="http://www.wellitworkedlasttime.com/robbie/wp-content/uploads/2008/07/googlehack1.jpg" alt="today’s googlehack" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.wellitworkedlasttime.com/robbie/index.php/2008/google-trends-hacked/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>wordpress &#8216;pretty&#8217; permalinks</title>
		<link>http://www.wellitworkedlasttime.com/robbie/index.php/2008/wordpress-pretty-permalinks/</link>
		<comments>http://www.wellitworkedlasttime.com/robbie/index.php/2008/wordpress-pretty-permalinks/#comments</comments>
		<pubDate>Tue, 08 Jul 2008 23:25:36 +0000</pubDate>
		<dc:creator>robbie</dc:creator>
				<category><![CDATA[site]]></category>

		<guid isPermaLink="false">http://www.wellitworkedlasttime.com/robbie/?p=38</guid>
		<description><![CDATA[one thing about brinkster that cannot be criticised is their support. over the last 7 years i&#8217;ve had nothing but responsive - 24/7 &#8211; usually within minutes by email and now instantly via their live support. not only is it quick, its also technically knowledgeable &#8211; even at the first line. when there are issues, they get escalated very quickly [...]]]></description>
			<content:encoded><![CDATA[<p>one thing about <a href="http://www.brinkster.com/" title="brinkster web hosting">brinkster</a> that cannot be criticised is their support. over the last 7 years i&#8217;ve had nothing but responsive - 24/7 &#8211; usually within minutes by email and now instantly via their live support. not only is it quick, its also technically knowledgeable &#8211; even at the first line. when there are issues, they get escalated very quickly to technical specialists who, in my experience, sort things out there and then. having wasted a good hour searching for how to make <a href="http://codex.wordpress.org/Using_Permalinks" title="wordpress codex">wordpress</a> <a href="http://www.pagesofink.com/index.php/archive/upgrading-to-wordpress-25-on-brinkster/" title="'use linux instead' solution">permalinks</a> <a href="http://wordpress.org/support/topic/164360/page/4" title="wtf? help! wtf?">pretty</a> on brinkster&#8217;s IIS, i asked them the question. you cant&#8230;</p>
<p><span style="color: #1f497d" lang="EN-US"><font face="Calibri">Hello,</font></span><span style="color: #1f497d" lang="EN-US"><font face="Calibri"> </font></span><span style="color: #1f497d" lang="EN-US"><span style="color: #1f497d" lang="EN-US"><font face="Calibri">For security reasons on iis we do not install a url re &#8211; write engine. </font></span><span style="color: #1f497d" lang="EN-US"><font face="Calibri"> </font></span></span></p>
<p style="margin: 0cm 0cm 0pt" class="MsoNormal"><span style="color: #1f497d" lang="EN-US"><font face="Calibri">Thank you</font></span></p>
<p>Really? Ah, that&#8217;d be why then.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.wellitworkedlasttime.com/robbie/index.php/2008/wordpress-pretty-permalinks/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>new site</title>
		<link>http://www.wellitworkedlasttime.com/robbie/index.php/2008/new-site/</link>
		<comments>http://www.wellitworkedlasttime.com/robbie/index.php/2008/new-site/#comments</comments>
		<pubDate>Mon, 07 Jul 2008 22:30:56 +0000</pubDate>
		<dc:creator>robbie</dc:creator>
				<category><![CDATA[site]]></category>

		<guid isPermaLink="false">http://www.wellitworkedlasttime.com/robbie/?p=35</guid>
		<description><![CDATA[well now, first post in almost 5 years &#8211; and no, I&#8217;m not between contracts! I&#8217;ve just finished migrating the both the company site and my blog over to use Expression and Wordpress respectively. Previously, I&#8217;d hand-crafted both myself, which partly explains why I&#8217;d only ever update/blog on those rare occasions I had the time. in a [...]]]></description>
			<content:encoded><![CDATA[<p>well now, first post in almost 5 years &#8211; and no, I&#8217;m not between contracts! I&#8217;ve just finished migrating the both the <a title="company homepage" href="http://www.wellitworkedlasttime.com">company</a> site and my blog over to use <a title="Microsoft Expression" href="http://www.microsoft.com/expression/products/Overview.aspx?key=web" class="broken_link">Expression</a> and <a title="Wordpress" href="http://wordpress.org/">Wordpress</a> respectively. Previously, I&#8217;d hand-crafted both myself, which partly explains why I&#8217;d only ever update/blog on those rare occasions I had the time. in a <a title="xhtml compliance" href="http://www.http://www.wellitworkedlasttime.com/robbie/index.php/2003/code-vsnet-and-xhml-compliance/" class="broken_link">previous post</a> i complained about lack of standards compliance in tools, and that was the primary why (in 2001) I chose to do it myself. Luckily things have moved on since then, and I&#8217;m impressed by <a title="Microsoft Expression" href="http://www.microsoft.com/expression/products/Overview.aspx?key=web" class="broken_link">Expression</a> which is a perfectly nice little tool that permits full control over the output. indeed it sells itself on its standards support and, as it&#8217;s available via <a title="msdn" href="http://msdn.microsoft.com/en-us/subscriptions/default.aspx">msdn subscription</a>, i thought I&#8217;d give it a try. Remarkably, it generates output identical to that previously, but provides simplified management via templates and master pages. i use a single .dht (dynamic html template) in which one defines static content (which applies to all pages associated with the template) and then those areas where each instance page can override template content. it works with .aspx also, meaning dynamic and static content can share the same html basis, without recourse to using master pages just for textual layout. clearly designed for non-programmers - it&#8217;s a doddle to use.</p>
<p>As for Wordpress, my choice was admittedly made for me by my <a title="brinkster web hosting" href="http://www.brinkster.com">hosting provider</a>, who <a title="brinkster and wordpress" href="http://wordpress.org/tags/brinkster">support</a> it, but it seems perfectly adequate after a days use. It imported the rss output from my old handcrafted blog without any problem, and I&#8217;m sure I could style the output to closely match the look and feel of my old blog and current <a title="company homepage" href="http://www.wellitworkedlasttime.com">company</a> site. if I had the time and inclination. but hopefully i&#8217;ll have time to blog, rather than write xhtml and css in future though&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.wellitworkedlasttime.com/robbie/index.php/2008/new-site/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>bandwidth</title>
		<link>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-bandwidth/</link>
		<comments>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-bandwidth/#comments</comments>
		<pubDate>Tue, 12 Aug 2003 11:59:59 +0000</pubDate>
		<dc:creator>robbie</dc:creator>
				<category><![CDATA[site]]></category>

		<guid isPermaLink="false">http://www.wellitworkedlasttime.com/robbie/?p=6</guid>
		<description><![CDATA[thanks to google and recent newsgroup posts, the hits on this site have gone through the roof over the past week, using more bandwidth in a day than was previously used in a month. so to conserve that expensive resource i&#8217;ve consolidated the site a bit and zipped up all stray documents. in an uncharacteristic [...]]]></description>
			<content:encoded><![CDATA[<p>thanks to google and recent newsgroup posts, the hits on this site have gone through the roof over the past week, using more bandwidth in a day than was previously used in a month. so to conserve that expensive resource i&#8217;ve consolidated the site a bit and zipped up all stray documents. in an uncharacteristic act of madness, I also removed the old files, which will mean some broken external links (doh!).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-bandwidth/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>log parser</title>
		<link>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-log-parser/</link>
		<comments>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-log-parser/#comments</comments>
		<pubDate>Wed, 06 Aug 2003 11:59:59 +0000</pubDate>
		<dc:creator>robbie</dc:creator>
				<category><![CDATA[site]]></category>

		<guid isPermaLink="false">http://www.wellitworkedlasttime.com/robbie/?p=5</guid>
		<description><![CDATA[as is not uncommon, my ISP uses load balanced web servers, which can make log file analysis a bit of a pain. i prefer to use WebTrends, whose fascist licensing policy would mean purchasing the most expensive edition plus extra licenses for each load balanced server whose log files i want to report on. i [...]]]></description>
			<content:encoded><![CDATA[<p>as is not uncommon, my <a title="Brinkster" href="http://www.brinskter.com">ISP</a> uses load balanced web servers, which can make log file analysis a bit of a pain. i prefer to use <a title="WebTrends" href="http://www.webtrends.com">WebTrends</a>, whose fascist licensing policy would mean purchasing the most expensive edition plus extra licenses for each load balanced server whose log files i want to report on. i dont think so.</p>
<p>enter the excellent <a title="Log Parser 2" href="http://www.iisfaq.com/default.aspx?View=A525&amp;P=141">Log Parser 2</a> which is also part of the IIS-6 SDK. it&#8217;s a simple command line util that can parse, query and convert web log files using SQL syntax, and it can also consolidate multiple server logs into a file that webtrends will happily consume without insisting on extra cash.</p>
<p><code>logparser "SELECT * FROM d:logs*.log TO d:logsall.log ORDER BY date, time ASC" -i:IISW3C -o:W3C</code></p>
<p>this takes all my current extended IIS logs, consolidates the entries in date time order (otherwise webtrends can become petulant) and produces a single log file in W3C format. sweet. as an aside in a previous <a title="browser test reults" href="http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-browser-test-results/">post</a> i&#8217;d estimated that the site should view as intended in over 96% over broswers. interestingly, based on site stats, the actual figure exceeds 99%.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-log-parser/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>server side smtp</title>
		<link>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-server-side-smtp/</link>
		<comments>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-server-side-smtp/#comments</comments>
		<pubDate>Fri, 25 Jul 2003 11:59:59 +0000</pubDate>
		<dc:creator>robbie</dc:creator>
				<category><![CDATA[security]]></category>
		<category><![CDATA[site]]></category>

		<guid isPermaLink="false">http://www.wellitworkedlasttime.com/robbie/?p=9</guid>
		<description><![CDATA[Finally got round to updating all client &#8216;mailto&#8217; links to a server side C# SMTP implementation. though pretty basic it works well enough, despite my ISP&#8217;s constant tinkering with the web servers config.
]]></description>
			<content:encoded><![CDATA[<p>Finally got round to updating all client &#8216;mailto&#8217; links to a server side C# SMTP implementation. though pretty basic it works well enough, despite my <a href="http://www.brinkster.com" title="Brinkster">ISP</a>&#8217;s constant tinkering with the web servers config.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-server-side-smtp/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>privacy statement and p3p</title>
		<link>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-privacy-statement-and-p3p/</link>
		<comments>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-privacy-statement-and-p3p/#comments</comments>
		<pubDate>Mon, 21 Jul 2003 11:59:59 +0000</pubDate>
		<dc:creator>robbie</dc:creator>
				<category><![CDATA[privacy]]></category>
		<category><![CDATA[site]]></category>

		<guid isPermaLink="false">http://www.wellitworkedlasttime.com/robbie/?p=10</guid>
		<description><![CDATA[I finally made the site P3P compliant, and it was a bit of a hassle:
i created an html privacy page, handcrafted the required xml policy reference and policy files and added the meta element to them on all my pages. it would validate okay, but IE peristed on blocking some files and issuing a privacy [...]]]></description>
			<content:encoded><![CDATA[<p>I finally made the site <a href="http://www.w3.org/P3P/" title="W3C P3P">P3P</a> compliant, and it was a bit of a hassle:</p>
<p>i created an html privacy page, handcrafted the required xml policy reference and policy files and added the meta element to them on all my pages. it would <a href="http://www.w3.org/P3P/validator.html" title="W3C P3P Validator">validate</a> okay, but IE peristed on blocking some files and issuing a privacy report warning.</p>
<p>the only thing i hadn&#8217;t done was to implement the &#8216;compact&#8217; http header, which is optional in terms of P3P, so I supposed IE must be looking for that. but then, i thought, that couldnt be right &#8211; hosted static sites &#8211; of which there are more than a few &#8211; couldnt possibly generate that header (without access to the web server&#8217;s admin), and if IE was basing its checks on that, then&#8230;</p>
<p>well, wouldnt be the first time a browser vendor &#8216;interpreted&#8217; the standard for their own commericial ends; and the <a href="http://msdn.microsoft.com/library/default.asp?url=/workshop/security/privacy/overview/createprivacypolicy.asp" title="MSDN Online">msdn doco</a> says, &#8220;<em>Internet Explorer 6 uses these compact policies to filter cookies based on a user&#8217;s privacy preferences</em>&#8220;.</p>
<p>hmmm. without either a header, a meta element, or a &#8216;well known location&#8217; &#8211; /w3c/p3p.xml &#8211; (all of which are optional in the spec) there&#8217;s no way for a user agent to determine the presence of a P3P policy or not. and that&#8217;s one of the problems i have with the spec &#8211; to be be successfully implemented, to enable the implementation of the spec, specific requirements surely have to be placed on user agents, and here it falls downs. for the most part the P3P spec is only five things: an xml locator file, the xml policy file, a &#8216;well-known location&#8217; for the previous two, an http header extension (the so called &#8216;compact policy&#8217;), or an xhtml extension (e.g. meta element). the msdn link above suggests that the first four are required to stop IE blocking and issuing a privacy report warning.</p>
<p>however, after some experimenting setting cookies both with and without the header, it turns out i hadn&#8217;t added the optional <cookie-include></cookie-include>tag in my policy reference file, and that&#8217;s what IE was really looking for. if only the doco had been clearer and right&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-privacy-statement-and-p3p/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>browser test results</title>
		<link>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-browser-test-results/</link>
		<comments>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-browser-test-results/#comments</comments>
		<pubDate>Thu, 03 Jul 2003 11:59:59 +0000</pubDate>
		<dc:creator>robbie</dc:creator>
				<category><![CDATA[site]]></category>

		<guid isPermaLink="false">http://www.wellitworkedlasttime.com/robbie/?p=18</guid>
		<description><![CDATA[After some discussion in the bar last night over my use of CSS-2 for positioning and strict standards compliance in this site, I&#8217;m putting up the results of the browser tests&#8230;
Summary of Results
The site displays well at 800&#215;600 (even better at higher resolutions) in all major browsers on all major platforms, the site degrades gracefully [...]]]></description>
			<content:encoded><![CDATA[<p>After some discussion in the bar last night over my use of CSS-2 for positioning and strict standards compliance in this site, I&#8217;m putting up the results of the browser tests&#8230;</p>
<p><strong>Summary of Results</strong></p>
<p>The site displays well at 800&#215;600 (even better at higher resolutions) in all major browsers on all major platforms, the site degrades gracefully in older broswers with loss of presentation, but not content. Based on current <a href="http://www.thecounter.com/stats/" title="The Counter Statistics Website">browser stats</a>, this site should display as it is intended in over 96% of current browsers. Testing was conducted online using the excellent <a href="http://www.browsercam.com" title="BroswerCam Website">BrowserCam</a>. Tests were performed using the following configurations:</p>
<ul>
<li>Internet Explorer 5.0, 5.5 and 6.0 on Windows 2000</li>
<li>Netscape Navigator 4.78, 4.8, 6.2 and 7.0 on Windows 2000, Macintosh, Linux</li>
<li>Opera 6.0 on Windows 2000 and Macintosh</li>
<li>Mozilla 1.3 on Windows 2000 and Linux</li>
<li>AOL 7.0 on Windows 2000</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-browser-test-results/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>open for business</title>
		<link>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-open-for-business/</link>
		<comments>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-open-for-business/#comments</comments>
		<pubDate>Tue, 01 Jul 2003 11:59:59 +0000</pubDate>
		<dc:creator>robbie</dc:creator>
				<category><![CDATA[site]]></category>

		<guid isPermaLink="false">http://www.wellitworkedlasttime.com/robbie/?p=23</guid>
		<description><![CDATA[Well, at long last I&#8217;ve finally got round to getting this properly up and running. Its taken a while, primarily thanks to too many other things happening, rather than effort, but still has a way to go. Today I put together the new site structure, layout and initial content.
I intend to put here certification resources, [...]]]></description>
			<content:encoded><![CDATA[<p>Well, at long last I&#8217;ve finally got round to getting this properly up and running. Its taken a while, primarily thanks to too many other things happening, rather than effort, but still has a way to go. Today I put together the new site structure, layout and initial content.</p>
<p>I intend to put here certification resources, technical papers, code samples and the like &#8211; there&#8217;s not a great deal at the moment, but it&#8217;s a start&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.wellitworkedlasttime.com/robbie/index.php/2003/site-update-open-for-business/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
