When activating certificate on an older site all seemed fine. Even with a rewrite rule to force people from http to https things seemed fine. However, I got a report that people had trouble getting on to the site which puzzled me.
Then I got one of the reports which was a "A potentially dangerous Request.Path value was detected from the client (:)." error. This error was the result of clicking on a link in a mail sent by NS.
I went ahead to check the log and found this:
2017-09-22 08:18:12,186 [16] ERROR Umbraco.Core.UmbracoApplicationBase - [Thread 325] An unhandled exception occurred
System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.FormatException: Index (zero based) must be greater than or equal to zero and less than the size of the argument list.
at System.Text.StringBuilder.AppendFormatHelper(IFormatProvider provider, String format, ParamsArray args)
at System.String.FormatHelper(IFormatProvider provider, String format, ParamsArray args)
at System.String.Format(String format, Object[] args)
at NewsletterStudio.Infrastucture.Compression.LegacyEncryptionCompressor.Decompress(String compressedText)
at NewsletterStudio.Infrastucture.Compression.LegacySimpleAESProxyCompressor.Decompress(String compressedText)
at NewsletterStudio.External.TrackPixel.ProccessQueryString()
at NewsletterStudio.External.TrackPixel.Page_Load(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP.umbraco_newsletterstudio_tracking_trackpixel_aspx.ProcessRequest(HttpContext context) in c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\3c946d77\9bf90825\App_Web_trackpixel.aspx.e621b34f.3shjdqrh.0.cs:line 0
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
repeatedly.
So, I commented the rewrite rule out and it stopped.
Anyone have an idea how to solve or work around this?
Did you get the "A potentially dangerous Request.Path value was detected from the client (:)."-error only on https? That sounds really strange, maybe your rewrite is adding something strange to the url?
Or is it the error that you posted from the log? "Index (zero based) must be greater than or equal to zero and less than the size of the argument list.", are you only getting this on https as well?
Issue with https - NS 1.4.5.2/Umbraco 6.1.3
Hi
When activating certificate on an older site all seemed fine. Even with a rewrite rule to force people from http to https things seemed fine. However, I got a report that people had trouble getting on to the site which puzzled me.
Then I got one of the reports which was a "A potentially dangerous Request.Path value was detected from the client (:)." error. This error was the result of clicking on a link in a mail sent by NS.
I went ahead to check the log and found this:
repeatedly.
So, I commented the rewrite rule out and it stopped.
Anyone have an idea how to solve or work around this?
Kind regards, Bruno
Hi!
Did you get the "A potentially dangerous Request.Path value was detected from the client (:)."-error only on https? That sounds really strange, maybe your rewrite is adding something strange to the url?
Or is it the error that you posted from the log? "Index (zero based) must be greater than or equal to zero and less than the size of the argument list.", are you only getting this on https as well?
Cheers!
// m
Hi Markus
The rewrite looks like this:
I found it odd as well.
There error in the log didn't occur before the rewrite was active, and hasn't occured since it was deactivated.
I noticed something else: While the "Index (zero based).." error was occuring newsletterSendout responded with false:
After the rewrite was deactivated it responds with true.
When the rewrite was activated I didn't notice any odd things in the URLs when accessing the site in a browser.
Kind regards, Bruno
is working on a reply...