.NET Warnings on Windows Logs

A potentially dangerous Request.Path value was detected from the client (*)

The * character is not allowed in the path of the URL, but there is no problem using it in the query string:

http://localhost:3286/Search/?q=test*

It's not an encoding issue, the * character has no special meaning in an URL, so it doesn't matter if you URL encode it or not. You would need to encode it using a different scheme, and then decode it.

For example using an arbitrary character as escape character:

query = query.Replace("x", "xxx").Replace("y", "xxy").Replace("*", "xyy");

And decoding:

query = query.Replace("xyy", "*").Replace("xxy", "y").Replace("xxx", "x");

Comments

SQL Server

SQL Server Its been a while that I have updated my blog. Though Databases and SQL was something that I used to stay away as much as possible because for some reasons, I got to work on these all the day for 8-9 hours and sometimes haunting in the nights and weekends as well. However, it has been a good journey so far and I found some interesting stuff in SQL Server. So, this triggered an idea a couple of weeks back to share some cool stuff that I am learning in SQL Server over numerous sources. Hope I can make this a good series. As there are not much visitors to my blog, le...

An TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The TLS connection request has failed.

If the certificate being used on the server was generated using the Legacy Key option in the certificate request form, the private key for that certificate will be stored in Microsoft's legacy Cryptographic API framework. When the web server tries to process requests using its new, Cryptographic Next Generation (CNG) framework, it appears that something related to the RSA private key stored in the legacy framework is unavailable to the new framework. As a result, the use of the RSA cipher suites is severely limited. To avoid the issue, you can try to generate the certificate request using the CNG Key template in the custom certificate request wizard.

One-third of people 'would upgrade' to a Facebook phone - is Zuckerberg's latest project a serious rival to iPhone?

One-third of phone users would definitely upgrade to a Facebook phone - and 73% think the phone is a ‘good idea’. News of the phone emerged, with sources claiming that Facebook had hired ex-Apple engineers to work on an ‘official’ Facebook phone. It’s not the first Facebook phone to hit the market – the social network giant has previously partnered with INQ and HTC to produce Facebook-oriented handsets, including phones with a built-in ‘Like’ button. It could be a major hit – a flash poll of 968 people conducted by MyVoucherCodes found that 32% of phone users would upgrade as soon as it became available. The key to its success could be porting apps to mobile – something Facebook is already doing. Separate camera and chat apps already separate off some site functions, and third-party apps will shortly be available via a Facebook app store. Of those polled, 57% hoped that it would be cheaper than an iPhone – presumably support...

Anything and Everything

Search This Blog