This is a migrated thread and some comments may be shown as answers.

RadCompression TroubleShoot

15 Answers 251 Views

ScriptManager and StyleSheetManager

This is a migrated thread and some comments may be shown as answers.

15 Answers, 1 is accepted

answered on 10 Nov 2009, 01:29 PM

Hello Matthew,

I am sorry to hear that you are having difficult time working with our RadCompression module. We are doing our best to address any reported issues that are confirmed by our Support Staff/QA engineers. However, there is always a possibility that an issue or a bug can slip through our test engine and get into production code.

That is why I suggest you isolate a working case (using v2009.3.1103 of the suite) which illustrates the abnormality and send it enclosed to a standard support ticket. We will examine your code/debug the sample locally and will get back to you with our findings.

The IIS7 built-in compression can be an alternative to RadCompression.

Kind regards,
Sebastian
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

answered on 02 Dec 2009, 10:00 AM

Hi Sebastian,

Yeh appreciate the need for repeat test case, but could you help me out with some guidelines of how I can troubleshoot this to narrow down causes. I really want this to work as it will reduce my payload massively.

1. Need to find out why its stopping postback on certain pages, I assume it could be my jquery conflicting somehow? could this be the case?

NEW: Just noticed this IMPORTANT INFO.

http://localhost/pi40/default.aspx - works fine on postback fro click/enter ETC..
http://localhost/pi40/ - does not work as above.

Does this help?

Also, I do employ some url rewriting for seo, but obviously have no clue as to how this could affect radcompresson?? any ideas.
I use this scott gu? code for helping with css paths and the like + IISAPI REWRITE by helicon, its worked for years.

---

    
            Imports Microsoft.VisualBasic  
        
            Public Class FormRewriterControlAdapter  
        
                Inherits System.Web.UI.Adapters.ControlAdapter  
        
                Protected Overrides Sub Render(ByVal writer As System.Web.UI.HtmlTextWriter)  
        
                    MyBase.Render(New RewriteFormHtmlTextWriter(writer))  
        
                End Sub 
        
            End Class 
        
            Public Class RewriteFormHtmlTextWriter  
        
                Inherits HtmlTextWriter  
        
                Sub New(ByVal writer As HtmlTextWriter)  
        
                    MyBase.New(writer)  
        
                    Me.InnerWriter = writer.InnerWriter  
        
                End Sub 
        
                Sub New(ByVal writer As System.IO.TextWriter)  
        
                    MyBase.New(writer)  
        
                    MyBase.InnerWriter = writer  
        
                End Sub 
        
                Public Overrides Sub WriteAttribute(ByVal name As String, ByVal value As String, ByVal fEncode As Boolean)  
        
                    ' If the attribute we are writing is the "action" attribute, and we are not on a sub-control,   
        
                    ' then replace the value to write with the raw URL of the request - which ensures that we'll  
        
                    ' preserve the PathInfo value on postback scenarios  
        
                    If (name = "action") Then 
        
                        Dim Context As HttpContext  
        
                        Context = HttpContext.Current  
        
                        If Context.Items("ActionAlreadyWritten") Is Nothing Then 
        
                            ' Because we are using the UrlRewriting.net HttpModule, we will use the   
        
                            ' Request.RawUrl property within ASP.NET to retrieve the origional URL  
        
                            ' before it was re-written.  You'll want to change the line of code below  
        
                            ' if you use a different URL rewriting implementation.  
        
                            ' local iis with rewrite is now the required solution  
        
                            value = Context.Request.ServerVariables("HTTP_X_REWRITE_URL")  
        
                            'If HttpContext.Current.Request.Url.Host.ToLower() = "localhost" And Global.TestSite() Then  
        
                            '    value = Context.Request.RawUrl  
        
                            'Else  
        
                            '    ' live  
        
                            '    value = Context.Request.ServerVariables("HTTP_X_REWRITE_URL")  
        
                            'End If  
        
                            ' Indicate that we've already rewritten the <form>'s action attribute to prevent  
        
                            ' us from rewriting a sub-control under the <form> control  
        
                            Context.Items("ActionAlreadyWritten") = True 
        
                        End If 
        
                    End If 
        
                    MyBase.WriteAttribute(name, value, fEncode)  
        
                End Sub 
        
            End Class

---

2. Then find out why it works on dev but not production/test server?

i.e. How can I step through the code debug js/.net to help isolate the issue.

I will try to strip down my code to the bare minimum and create a test solution, but there is a lot of working parts :(

Thanks
Matt

answered on 04 Dec 2009, 12:33 PM

Hello Matthew,

Unfortunately from the provided details I am still not able to trace the core of the abnormality or provide suggestions what is causing it/how to fix it.

Does disabling the url rewriter module or replacing RadScriptManager with regular MS ScriptManager fixes the erroneous behavior? You may also compare the behavior between ajax requests and plain postbacks disabling the ajax in your app and setting enablePostbackCompression = true for RadCompression as explained here.

Also using the regular .NET code debugging techniques to follow the execution of your code and pinpoint the place when the issue occurs is something you can consider. Fiddler is a web debugging tool that can help you monitor the traffic between the client and your production server.

Best regards,
Sebastian
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

answered on 04 Dec 2009, 02:17 PM

Hi Sebastian,

Better news, It 'looks like' it is definetly the formrewriter.vb conflicting here with radcompression (and only this root url, i.e. /pi40/ not /pi40/default.aspx)! no idea why. Commenting out the xml in the form.browser xml file makes it post back ok no problem.

I got it from this article - http://weblogs.asp.net/scottgu/archive/2007/02/26/tip-trick-url-rewriting-with-asp-net.aspx

We use ISAPIRewrite and IIS7.

fyi: RAD vs MSScriptManager makes no difference.

Could you please install this into your environment and see how radcompression is working with it? hope we can get to the bottom of it.

Many Thanks
Matt

answered on 15 Dec 2010, 12:56 PM

Hi to all,

I found a solution with the problem above.

Precondition:
- Developing with ASP.NET 4.0
- Using RadCompression Module
- Call the default page (Ex. www.contoso.com , not www.contoso.com/default.aspx) without specify page.

In the ASP.NET 4.0 one important change is that if you call the default page without specify page it set the attribute ACTION for the tag FORM to be empty (Ex. <form action="" ... />); instead if you specify page like default.aspx the engine set attribute with the relative path of page specified (Ex. <form action="default.aspx" ... />).

What happen is an incapacity for the modules to access to page properties: viewstate,form variables,etc. (for more detail read this http://jai-on-asp.blogspot.com/2010/06/changes-and-differences-between-aspnet.html at paragraph "Event Handlers Might Not Be Not Raised in a Default Document in IIS 7 or IIS 7.5 Integrated Mode"

So, the solution for me is to set Page.Form.Action = "Default.aspx" in page init event only for the default page.

Have a nice xmas!
Michael Sogos

Product Bundles

DevCraft

Web

Mobile

Document Management

Desktop

Reporting & Mocking

Automated Testing

CMS

UI/UX Tools

Debugging

Free Tools

Support and Learning

Productivity and Design Tools

RadCompression TroubleShoot

15 Answers, 1 is accepted