Daniel Miller
Posts:44
| | 03/07/2007 11:30 AM |
| I am currently having a problem opening PDF files. When PageBlaster is on and I try to open a pdf document for some users it gives them a blank screen then they have to open acrobat manaully to see the file. Some users are only given the option to save or cancel. When I have PageBlaster off it opens the document the right way and right away.
How do I get around this. I have set the following in my exclude paths under the Snapsis.PageBlaster.config file: pattern="LinkClick.aspx"excludeFrom="All" | | | |
|
|
|
John Mitchell
Posts:3241
| | 03/07/2007 11:37 AM |
| If it is delivering it through the LinkClick.aspx page then that should work.
Also, make sure that you have also removed the core compression module from the web.config.
If you can show me a link that is having the problem then I can look at it with Fiddler to see if I can determine any other problem.
| | | |
|
Daniel Miller
Posts:44
| | 03/07/2007 11:44 AM |
| I have removed compression from the web.config file by commenting it out with .
You can link to any of the documents on our home page. www.orcities.org. | | | |
|
Daniel Miller
Posts:44
| | 03/07/2007 11:44 AM |
| | The key thing is it acts different for each user. It is not consistent about the conclusion unless pagablaster is disabled. | | | |
|
John Mitchell
Posts:3241
| | 03/07/2007 12:33 PM |
| I tried the document links on the home page and found that some are direct to .Pdf files, while others go through the LinkClick page.
You might try adding another exclude path:
pattern="\.PDF" excludeFrom="All" to see if it helps. | | | |
|
Daniel Miller
Posts:44
| | 03/07/2007 3:57 PM |
| | I tried this and it didn't work. | | | |
|
John Mitchell
Posts:3241
| | 03/07/2007 4:26 PM |
| All of the links I clicked on with PDF's worked without fail. Even the ones that were using LinkClick.aspx. Maybe it is a browser issue.
Also, PageBlaster automatically excludes any type of request that is not for a web page (like clicking on a link that ends in .pdf) . | | | |
|
Daniel Miller
Posts:44
| | 03/07/2007 4:30 PM |
| | As I said before it is not consistent. I have users that it works for but the majority either get save/cancel or a blank page. The one consistent thing is when I disable pageblaster everyone has it working just fine. | | | |
|
John Mitchell
Posts:3241
| | 03/07/2007 4:37 PM |
| Is it maybe different if they are logged in?
I don't see how PageBlaster could be inconsistent like that. I'm not saying it isn't happening, but it should either be on or off.
On the users that it doesn't work for, does it always fail if PageBlaster is on? If so, maybe it is something different that their browsers are sending to PageBlaster.
If you can find out what browser it always fails on, then I can monitor using that browser. | | | |
|
Daniel Miller
Posts:44
| | 03/07/2007 4:43 PM |
| | It fails for FireFox, Mozilla, IE 6 and 7 and for one for Mac users. From the research I have done the DNN compression utils will do the same thing unless you have compression off. I have also seen people say that is gzip that causes this. I know that page blaster uses gzip. I have eliminated any other problems by disabling pageblaster and running the site and not getting the problem. They are not receiving an error they are either not able to just open the document or they don't get acrobat to open at all. | | | |
|
John Mitchell
Posts:3241
| | 03/07/2007 5:11 PM |
| If you want, you can just disable compression, and still have caching.
pattern=".*" excludeFrom="Compression"
| | | |
|
Daniel Miller
Posts:44
| | 03/07/2007 5:20 PM |
| | I have tried that and it doesn't work either. I have also tried setting compress-level=None and it didn't work. | | | |
|
John Mitchell
Posts:3241
| | 03/07/2007 5:31 PM |
| I'm really at a loss. I have tried IE7 & FireFox, & Opera, but it never fails.
Maybe it is a proxy issue for some users. | | | |
|
Daniel Miller
Posts:44
| | 03/07/2007 5:35 PM |
| | Don't think that is it. I am having the same issue and I am connected to the server. What I have noticed is if a user has acrobat pro 60% have problems. If that have just reader it is about 20%. We are a high volume site and we host about 30 other sites. Each having the same problem. | | | |
|
John Mitchell
Posts:3241
| | 03/07/2007 5:43 PM |
| For the users that fail does it always fail? If so, we need to do some monitoring using their environment.
Are you familiar with Fiddler? It's a Microsoft program that lets you look at the details of web requests going to and from the browser.
By using that we can determine if PageBlaster is not getting excluded when it should.
| | | |
|
Daniel Miller
Posts:44
| | 03/07/2007 5:48 PM |
| | I have downloaded. Can you talk me through what I should do. | | | |
|
John Mitchell
Posts:3241
| | 03/07/2007 5:54 PM |
| Once you start it you can browse to the site and download a file. When it fails we need to look at the details of the request which you can find on the right under Session Inspector.
First click on the proper request in the left pane, one that says LinkClick, or PDF, then look at the session inspector and click on Raw.
If you copy and paste the raw request and response I may be able to see why it is failing. | | | |
|
Daniel Miller
Posts:44
| | 03/07/2007 6:05 PM |
| //PageBlaster Enabled
HTTP/1.1 200 OK
Date: Thu, 08 Mar 2007 00:04:52 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
content-disposition: inline; filename="Telecom_Release_Comp_Video_Franchising_FINAL-Web_3-5-07.pdf"
Content-Length: 235936
X-Snapsis-PageBlaster: v:2.1.1;c:-
Cache-Control: private
Content-Type: application/pdf; charset=UTF-8
| | | |
|
Daniel Miller
Posts:44
| | 03/07/2007 6:08 PM |
| //PageBlaster disabled
HTTP/1.1 200 OK
Date: Thu, 08 Mar 2007 00:07:34 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
content-disposition: inline; filename="Telecom_Release_Comp_Video_Franchising_FINAL-Web_3-5-07.pdf"
Content-Length: 235936
Cache-Control: private
Content-Type: application/pdf
| | | |
|
Daniel Miller
Posts:44
| | 03/07/2007 6:15 PM |
| | The only difference seems to be the charset on the enabled version and of course the refernece to pageblaster | | | |
|