My favorites | Sign in
Project Logo
                
Details: Show all Hide all

Last 30 days

  • Dec 03, 2009
    issue 19 (Sys.WebForms.PageRequestManagerParserErrorException error wi...) reported by rizaan.jappie   -   What steps will reproduce the problem? 1. LinkButton placed within a updatepanel to perform a ajax call 2. 3. What is the expected output? What do you see instead? The page is expected to make a ajax call. Error "Sys.WebForms.PageRequestManagerParserErrorException: " occurred. What version of the product are you using? On what operating system? Version 7 on windows xp SP2 Please provide any additional information below.
    What steps will reproduce the problem? 1. LinkButton placed within a updatepanel to perform a ajax call 2. 3. What is the expected output? What do you see instead? The page is expected to make a ajax call. Error "Sys.WebForms.PageRequestManagerParserErrorException: " occurred. What version of the product are you using? On what operating system? Version 7 on windows xp SP2 Please provide any additional information below.

Earlier this year

  • Nov 26, 2009
    issue 18 (IIS Runtime error page is shown instead of MOSS error page a...) reported by nikolaj.kaplan   -   I'm running an asp.net page deployed as an application page in MOSS 2007 the page is very simple and contains the following code: <asp:Button ID="Button1" runat="server" Text="Throw exception" onclick="Button1_Click" /> ... protected void Button1_Click(object sender, EventArgs e) { throw new ApplicationException(); } When I click the button I get a nice MOSS page with the error and a stack trace. When blowery is turned on however I get the following invalid html back. This is a complete view source: *************************** </pre></table></table></table></table></table></font></font></font></font>< /font></i></i></i></i></i></b></b></b></b></b></u></u></u></u></u><p>&nbsp; </p><hr> <html> <head> <title>Runtime Error</title> <style> body {font-family:"Verdana";font-weight:normal;font- size: .7em;color:black;} p {font-family:"Verdana";font-weight:normal;color:black;margin- top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin- top: -5px} H1 { font-family:"Verdana";font-weight:normal;font- size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font- size:14pt;color:maroon } pre {font-family:"Lucida Console";font-size: .9em} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; } </style> </head> <body bgcolor="white"> <span><H1>Server Error in '/' Application.<hr width=100% size=1 color=silver></H1> <h2> <i>Runtime Error</i> </h2></span> <font face="Arial, Helvetica, Geneva, SunSans-Regular, sans- serif "> <b> Description: </b>An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed. <br><br> <b>Details:</b> To enable the details of this specific error message to be viewable on the local server machine, please create a &lt;customErrors&gt; tag within a &quot;web.config&quot; configuration file located in the root directory of the current web application. This &lt;customErrors&gt; tag should then have its &quot;mode&quot; attribute set to &quot;RemoteOnly&quot;. To enable the details to be viewable on remote machines, please set &quot;mode&quot; to &quot;Off&quot;.<br><br> <table width=100% bgcolor="#ffffcc"> <tr> <td> <code><pre> &lt;!-- Web.Config Configuration File --&gt; &lt;configuration&gt; &lt;system.web&gt; &lt;customErrors mode=&quot;RemoteOnly&quot;/&gt; &lt;/system.web&gt; &lt;/configuration&gt;</pre></code> </td> </tr> </table> <br> <b>Notes:</b> The current error page you are seeing can be replaced by a custom error page by modifying the &quot;defaultRedirect&quot; attribute of the application's &lt;customErrors&gt; configuration tag to point to a custom error page URL.<br><br> <table width=100% bgcolor="#ffffcc"> <tr> <td> <code><pre> &lt;!-- Web.Config Configuration File --&gt; &lt;configuration&gt; &lt;system.web&gt; &lt;customErrors mode=&quot;On&quot; defaultRedirect=&quot;mycustompage.htm&quot;/&gt; &lt;/system.web&gt; &lt;/configuration&gt;</pre></code> </td> </tr> </table> <br> </body> </html> *************************** The even wierder thing is that if I request any page on the site right after an error has occured, the browser hangs for several minutes before returning a response. When the response returns it is as expected. No timeout occurs. This long delay occurs even though I start a new browser. And even though the first browser was IE and the new one is firefox. The delay does not occur if I provoke the error from one client pc and subsequent request a page from another client pc. All problems go away when turning blowery off. I can recreate the problem in developmen, preprod and production environment. Any ideas for debugging or fixing this problem? Regards, Nikolaj
    I'm running an asp.net page deployed as an application page in MOSS 2007 the page is very simple and contains the following code: <asp:Button ID="Button1" runat="server" Text="Throw exception" onclick="Button1_Click" /> ... protected void Button1_Click(object sender, EventArgs e) { throw new ApplicationException(); } When I click the button I get a nice MOSS page with the error and a stack trace. When blowery is turned on however I get the following invalid html back. This is a complete view source: *************************** </pre></table></table></table></table></table></font></font></font></font>< /font></i></i></i></i></i></b></b></b></b></b></u></u></u></u></u><p>&nbsp; </p><hr> <html> <head> <title>Runtime Error</title> <style> body {font-family:"Verdana";font-weight:normal;font- size: .7em;color:black;} p {font-family:"Verdana";font-weight:normal;color:black;margin- top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin- top: -5px} H1 { font-family:"Verdana";font-weight:normal;font- size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font- size:14pt;color:maroon } pre {font-family:"Lucida Console";font-size: .9em} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; } </style> </head> <body bgcolor="white"> <span><H1>Server Error in '/' Application.<hr width=100% size=1 color=silver></H1> <h2> <i>Runtime Error</i> </h2></span> <font face="Arial, Helvetica, Geneva, SunSans-Regular, sans- serif "> <b> Description: </b>An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed. <br><br> <b>Details:</b> To enable the details of this specific error message to be viewable on the local server machine, please create a &lt;customErrors&gt; tag within a &quot;web.config&quot; configuration file located in the root directory of the current web application. This &lt;customErrors&gt; tag should then have its &quot;mode&quot; attribute set to &quot;RemoteOnly&quot;. To enable the details to be viewable on remote machines, please set &quot;mode&quot; to &quot;Off&quot;.<br><br> <table width=100% bgcolor="#ffffcc"> <tr> <td> <code><pre> &lt;!-- Web.Config Configuration File --&gt; &lt;configuration&gt; &lt;system.web&gt; &lt;customErrors mode=&quot;RemoteOnly&quot;/&gt; &lt;/system.web&gt; &lt;/configuration&gt;</pre></code> </td> </tr> </table> <br> <b>Notes:</b> The current error page you are seeing can be replaced by a custom error page by modifying the &quot;defaultRedirect&quot; attribute of the application's &lt;customErrors&gt; configuration tag to point to a custom error page URL.<br><br> <table width=100% bgcolor="#ffffcc"> <tr> <td> <code><pre> &lt;!-- Web.Config Configuration File --&gt; &lt;configuration&gt; &lt;system.web&gt; &lt;customErrors mode=&quot;On&quot; defaultRedirect=&quot;mycustompage.htm&quot;/&gt; &lt;/system.web&gt; &lt;/configuration&gt;</pre></code> </td> </tr> </table> <br> </body> </html> *************************** The even wierder thing is that if I request any page on the site right after an error has occured, the browser hangs for several minutes before returning a response. When the response returns it is as expected. No timeout occurs. This long delay occurs even though I start a new browser. And even though the first browser was IE and the new one is firefox. The delay does not occur if I provoke the error from one client pc and subsequent request a page from another client pc. All problems go away when turning blowery off. I can recreate the problem in developmen, preprod and production environment. Any ideas for debugging or fixing this problem? Regards, Nikolaj
  • Aug 11, 2009
    issue 17 (Content cut off when using Server.Transfer) commented on by analogue...@gmail.com   -   I Thought you would like to know that I did come up with a somewhat ugly workaround after a few hours of fiddling. I use a Master page for the main template of the site. By appending blank lines to the end of the master page, it fixed the cutoff problem. The blank lines had to correlate to the amount of source code that was cut off normally. For example, if it was only cutting off one line, appending a single blank line to the Master page fixed the problem. If it was cutting off 10 lines, appending 10 blank lines to the end would do the trick. Not ideal, but what can you do. Thanks for pointing out the known error, I wasn't aware of that.
    I Thought you would like to know that I did come up with a somewhat ugly workaround after a few hours of fiddling. I use a Master page for the main template of the site. By appending blank lines to the end of the master page, it fixed the cutoff problem. The blank lines had to correlate to the amount of source code that was cut off normally. For example, if it was only cutting off one line, appending a single blank line to the Master page fixed the problem. If it was cutting off 10 lines, appending 10 blank lines to the end would do the trick. Not ideal, but what can you do. Thanks for pointing out the known error, I wasn't aware of that.
  • Aug 11, 2009
    issue 17 (Content cut off when using Server.Transfer) Status changed by blowery   -   Sadly, this is a known "bug" in ASP.NET. Server.Transfer doesn't work with response filters.
    Status: WontFix
    Sadly, this is a known "bug" in ASP.NET. Server.Transfer doesn't work with response filters.
    Status: WontFix
  • Aug 10, 2009
    issue 17 (Content cut off when using Server.Transfer) reported by analogue...@gmail.com   -   What steps will reproduce the problem? 1. Set up the HttpCompress Module 2. Set up a page that utilizes Server.Transfer and is compressed using the tool. 3. View the source of the page in the browser. What is the expected output? What do you see instead? The entire page should render. Instead, some of the content is cut off, appears to be a random amount and on occasion nothing is lost. What version of the product are you using? On what operating system? HttpCompress v7, IIS 6, ASP.NET 2.0 Please provide any additional information below. A strange bug, I have an unhandled exception HttpModule that utilizes Server.Transfer to send them to a specific page if an unhandled exception occurs. Often, when used in conjunction with the HttpCompress module, the last several lines of the source are cut off. Turning off the HttpCompress module causes the full source to render as expected. Tested without the unhandled exception module by setting up a simple server.transfer on another page ended up with the same results.
    What steps will reproduce the problem? 1. Set up the HttpCompress Module 2. Set up a page that utilizes Server.Transfer and is compressed using the tool. 3. View the source of the page in the browser. What is the expected output? What do you see instead? The entire page should render. Instead, some of the content is cut off, appears to be a random amount and on occasion nothing is lost. What version of the product are you using? On what operating system? HttpCompress v7, IIS 6, ASP.NET 2.0 Please provide any additional information below. A strange bug, I have an unhandled exception HttpModule that utilizes Server.Transfer to send them to a specific page if an unhandled exception occurs. Often, when used in conjunction with the HttpCompress module, the last several lines of the source are cut off. Turning off the HttpCompress module causes the full source to render as expected. Tested without the unhandled exception module by setting up a simple server.transfer on another page ended up with the same results.
  • Mar 18, 2009
    issue 13 (Doesn't work without trailing slash) Status changed by blowery   -   Should be fixed with the new v7 release.
    Status: Fixed
    Should be fixed with the new v7 release.
    Status: Fixed
  • Mar 18, 2009
    issue 16 (Compression don't work in production server.) commented on by blowery   -   Sounds like a configuration problem. Either your host isn't respecting the settings in web.config, has somehow prevented HttpModules from being used (very unlikely), or something is just set incorrectly. I'm not sure how I can debug it without any kind of repro case. Unless you can supply one, I'm going to close this as invalid.
    Sounds like a configuration problem. Either your host isn't respecting the settings in web.config, has somehow prevented HttpModules from being used (very unlikely), or something is just set incorrectly. I'm not sure how I can debug it without any kind of repro case. Unless you can supply one, I'm going to close this as invalid.
  • Mar 18, 2009
    issue 16 (Compression don't work in production server.) reported by ephillipe   -   I download the latest version of component and test in development enviroment. Everything works fine. Faster. But when I deploy my site, the compressor don't work. But the request header, is the same...
    I download the latest version of component and test in development enviroment. Everything works fine. Faster. But when I deploy my site, the compressor don't work. But the request header, is the same...
  • Mar 12, 2009
    issue 15 (IsIncludedMimeType) reported by in...@barnaland.is   -   Not really an issue, just didn't know where else to put it. Just wanted to share some changes that I made to the code, instead of having excludedMimeTypes I changed it to includedMimeTypes. I realized today that I hadn't excluded application/x-zip-compressed, so it started to compress a zip file, IIS had huge memory usage(compressing 800MB zip file) and resulted finally in a timeout. Who knows what other file types have been compressed that don't need compressing, such as video files. My include list is a lot shorter <includedMimeTypes> <add type="text/html" /> <add type="text/xml" /> <add type="text/css" /> <add type="application/x-javascript" /> </includedMimeTypes>
    Not really an issue, just didn't know where else to put it. Just wanted to share some changes that I made to the code, instead of having excludedMimeTypes I changed it to includedMimeTypes. I realized today that I hadn't excluded application/x-zip-compressed, so it started to compress a zip file, IIS had huge memory usage(compressing 800MB zip file) and resulted finally in a timeout. Who knows what other file types have been compressed that don't need compressing, such as video files. My include list is a lot shorter <includedMimeTypes> <add type="text/html" /> <add type="text/xml" /> <add type="text/css" /> <add type="application/x-javascript" /> </includedMimeTypes>
  • Jan 14, 2009
    r11 (v7 and upgrade format for vs 2008) committed by blowery   -   v7 and upgrade format for vs 2008
    v7 and upgrade format for vs 2008
  • Jan 14, 2009
    httpcompress_7_binary.zip.zip (HttpCompress v7) file uploaded by blowery
  • Jan 14, 2009
    issue 14 (Path handling in HttpModule.CompressContent is not robust) Status changed by blowery   -   Thanks. It's a good reminder that I should cut a new release though. :)
    Status: Fixed
    Thanks. It's a good reminder that I should cut a new release though. :)
    Status: Fixed
  • Jan 14, 2009
    issue 14 (Path handling in HttpModule.CompressContent is not robust) commented on by jfburdet   -   Hmm, sorry, I used code from http://blowery.org/code/httpcompress_6_net2_source.zip ! You can close this ticket ...
    Hmm, sorry, I used code from http://blowery.org/code/httpcompress_6_net2_source.zip ! You can close this ticket ...
  • Jan 14, 2009
    issue 14 (Path handling in HttpModule.CompressContent is not robust) Status changed by blowery   -   Why the +1 on the length? The current code in SVN just uses the length of the ApplicationPath bare.
    Status: Accepted
    Why the +1 on the length? The current code in SVN just uses the length of the ApplicationPath bare.
    Status: Accepted
  • Jan 14, 2009
    issue 10 (Doesn't work with Firefox 2 or 3.0.1) Status changed by blowery   -   Closing
    Status: Invalid
    Closing
    Status: Invalid
  • Jan 14, 2009
    issue 14 (Path handling in HttpModule.CompressContent is not robust) reported by jfburdet   -   Please consider changing in HttpModule.cs the line : string realPath = app.Request.Path.Remove(0, app.Request.ApplicationPath.Length+1); by string realPath = ""; if (app.Request.ApplicationPath.Length > 1) { realPath = app.Request.Path.Remove(0, app.Request.ApplicationPath.Length + 1); } else { realPath = app.Request.Path.Substring(1); } That will prevent exception throwing in some cases.
    Please consider changing in HttpModule.cs the line : string realPath = app.Request.Path.Remove(0, app.Request.ApplicationPath.Length+1); by string realPath = ""; if (app.Request.ApplicationPath.Length > 1) { realPath = app.Request.Path.Remove(0, app.Request.ApplicationPath.Length + 1); } else { realPath = app.Request.Path.Substring(1); } That will prevent exception throwing in some cases.

Older

  • Nov 13, 2008
    issue 13 (Doesn't work without trailing slash) reported by kvalcanti   -   What steps will reproduce the problem? 1. Deploy the application in a virtual directory, say app 2. Try to access the application at http://localhost/app (not http://localhost/app/ 3. What is the expected output? What do you see instead? It should redirect me to http://localhost/app/ Instead, the following stack trace shows up: [ArgumentOutOfRangeException: Index and count must refer to a location within the string. Parameter name: count] System.String.Remove(Int32 startIndex, Int32 count) +0 blowery.Web.HttpCompress.HttpModule.CompressContent(Object sender, EventArgs e) +180 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75 What version of the product are you using? On what operating system? Version 6 for .NET 2.0, Binary Only Please provide any additional information below.
    What steps will reproduce the problem? 1. Deploy the application in a virtual directory, say app 2. Try to access the application at http://localhost/app (not http://localhost/app/ 3. What is the expected output? What do you see instead? It should redirect me to http://localhost/app/ Instead, the following stack trace shows up: [ArgumentOutOfRangeException: Index and count must refer to a location within the string. Parameter name: count] System.String.Remove(Int32 startIndex, Int32 count) +0 blowery.Web.HttpCompress.HttpModule.CompressContent(Object sender, EventArgs e) +180 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75 What version of the product are you using? On what operating system? Version 6 for .NET 2.0, Binary Only Please provide any additional information below.
  • Aug 11, 2008
    issue 12 (An unhandled exception was generated during the execution of...) commented on by mmodrall1   -   Looks like the same one I figured out today. If your aspx page does a Response.End () before sending anything to the client, the Response.ContentType header is not set. Blowery is looking at that to determine if it is something it can compress. When the header is not there, it blows up.
    Looks like the same one I figured out today. If your aspx page does a Response.End () before sending anything to the client, the Response.ContentType header is not set. Blowery is looking at that to determine if it is something it can compress. When the header is not there, it blows up.
  • Aug 11, 2008
    issue 12 (An unhandled exception was generated during the execution of...) commented on by mmodrall1   -   Looks like the same one I figured out today. If your aspx page does a Response.End () before sending anything to the client, the Response.ContentType header is not set. Blowery is looking at that to determine if it is something it can compress. When the header is not there, it blows up.
    Looks like the same one I figured out today. If your aspx page does a Response.End () before sending anything to the client, the Response.ContentType header is not set. Blowery is looking at that to determine if it is something it can compress. When the header is not there, it blows up.
  • Aug 07, 2008
    issue 12 (An unhandled exception was generated during the execution of...) reported by ArvindGTL   -   What steps will reproduce the problem? >> Actually error is not reproducable, its happen sometime. The yello error page is displyed with below error. [NullReferenceException: Object reference not set to an instance of an object.] CompressionModule.CompressContent(Object sender, EventArgs e) +202 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep .Execute() +92 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64 It seems error comes while request goes foe compress.. What is the expected output? What do you see instead? the yellow error page displyed instead on actual resultpage. What version of the product are you using? On what operating system? Please provide any additional information below. We used callback in the page. Does it causes the error? Please help!!
    What steps will reproduce the problem? >> Actually error is not reproducable, its happen sometime. The yello error page is displyed with below error. [NullReferenceException: Object reference not set to an instance of an object.] CompressionModule.CompressContent(Object sender, EventArgs e) +202 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep .Execute() +92 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64 It seems error comes while request goes foe compress.. What is the expected output? What do you see instead? the yellow error page displyed instead on actual resultpage. What version of the product are you using? On what operating system? Please provide any additional information below. We used callback in the page. Does it causes the error? Please help!!
  • Jul 25, 2008
    issue 11 (Microsoft Report Viewer) reported by Esther.Andrew   -   What steps will reproduce the problem? 1.Use Microsoft Report Viewer on a page What is the expected output? What do you see instead? Report Viewer fails. What version of the product are you using? On what operating system? VS2008, Microsoft Report Viewer 9.0.0.0, asp.net 3.5 Please provide any additional information below. It would be useful to have a prominent note on how to make the module work with ajax and anthem. When someone puts the time in, the next major revision should support web service calls and ajax (if possible).
    What steps will reproduce the problem? 1.Use Microsoft Report Viewer on a page What is the expected output? What do you see instead? Report Viewer fails. What version of the product are you using? On what operating system? VS2008, Microsoft Report Viewer 9.0.0.0, asp.net 3.5 Please provide any additional information below. It would be useful to have a prominent note on how to make the module work with ajax and anthem. When someone puts the time in, the next major revision should support web service calls and ajax (if possible).
 
Hosted by Google Code