Friday, 4 January 2013
Dishonored
It was interesting to see that I got a different ending than my wife as I'd largely gone for the 'low chaos' route of trying to not kill people, whereas she'd gone through and had ended up on a 'high chaos' route. Characters reacted differently towards me and apparently even the ending part of the game played out differently for me because I hadn't gone through killing everyone. While good/bad systems have been in games for a while now, it was interesting to see this one play out as I genuinely had no idea that it would have that sort of effect on the game.
The level of choice as to how you played through the game was also impressive. Once you get out of the 'hub' area and off to the area where you're going to carry out your task you pretty much have free reign as to how you go about it. For instance, on the last level my wife opted to sneak as best she could through the front defences, which was problematic due to the number of guards and electric fences that were about, whereas when I attempted the same thing, I snuck my way around to one side and found an outlet pipe that I snuck into, bypassing pretty much all of the fuss. Then, once you reach your target, you get the option to outright kill them, or work out a way to take them out of the picture non-lethally.
There aren't many games I can think of that give you such a level of choice when playing through it, but Dishonored was a welcome change and while I don't feel another game in the series is needed, hopefully this isn't the last we see of this style of gameplay.
Thursday, 18 February 2010
IIS7 doesn't like +'s in your URL's
Request limits and URL processing
The following changes result due to additional restrictions on how IIS processes incoming requests and their URLs.
11) Request URLs containing unencoded “+” characters in the path (not querystring) is rejected by default
You will receive HTTP Error 404.11 – Not Found: The request filtering module is configured to deny a request that contains a double escape sequence.
This error occurs because IIS is by default configured to reject attempts to doubly-encode a URL, which commonly represent an attempt to execute a canonicalization attack.
Workaround:
1) Applications that require the use of the “+” character in the URL path can disable this validation by setting the allowDoubleEscaping attribute in thesystem.webServer/security/requestFiltering configuration section in the application’s web.config. However, this may make your application more vulnerable to malicious URLs:
As it says, I wouldn't use this for an externally facing site as it can make it less secure, but mine is for internal use only.