Forum Discussion

JimT02's avatar
JimT02
Icon for Nimbostratus rankNimbostratus
May 20, 2014

The file is damaged and could not be repaired opening pdf file

getting the following ie9 browser error when opening a pdf document: 'The file is damaged and could not be repaired'.

 

A direct open from the IIS server is OK. But opening this (and a few other pdf's) thru the F5 LTM proxy results in the damaged error message.

 

16 Replies

  • Ah, I think the problem is with the STREAM::enable command and the STREAM_MATCHED event. Try putting your STREAM expression directly inside the iRule and use a blank generic STREAM profile:

    when HTTP_REQUEST { 
        HTTP::header remove Accept-Encoding
        STREAM::disable 
    } 
    when HTTP_RESPONSE {
        if { [HTTP::header Content-Type] contains "text" } {
            STREAM::expression {@https://pinet.pekininsurance.us@http://pidev.pekininsurance.com@ @https://12.179.10.177@http://pidev.pekininsurance.com@ @https://pimodel.pekininsurance.us@http://pidev.pekininsurance.com@ @https://deviis01@http://pidev.pekininsurance.com@ @https://DEVIIS01@http://pidev.pekininsurance.com@ @https://www.pekininsurance.us@http://tlpar.pekininsurance.com:8085@ @https://12.30.140.250@http://tlpar.pekininsurance.com:8085@ @https://www.pekininsurance.us:8095@http://tlpar.pekininsurance.com:8085@ @https://12.30.140.250:8095@http://tlpar.pekininsurance.com:8085@ @https://10.2.1.1:8085@http://tlpar.pekininsurance.com:8085@ @https://10.2.1.3:8085@http://tlpar.pekininsurance.com:8085@ @https://12.30.143.55:8095@http://tlpar.pekininsurance.com:8085@ @www.pekininsurance.us:8095@tlpar.pekininsurance.com:8085@ @12.30.140.250:8095@tlpar.pekininsurance.com:8085@ @10.2.1.1:8085@tlpar.pekininsurance.com:8085@ @10.2.1.3:8085@tlpar.pekininsurance.com:8085@ @12.30.143.55:8095@tlpar.pekininsurance.com:8085@ @pinet.pekininsurance.us@pidev.pekininsurance.com@ @12.179.10.177@pidev.pekininsurance.com@ @pimodel.pekininsurance.us@pidev.pekininsurance.com@ @deviis01@pidev.pekininsurance.com@ @DEVIIS01@pidev.pekininsurance.com@ @www.pekininsurance.us@tlpar.pekininsurance.com:8085@ @12.30.140.250@tlpar.pekininsurance.com:8085@ @10.2.1.1@tlpar.pekininsurance.com:8085@ @10.2.1.3@tlpar.pekininsurance.com:8085@ @12.30.143.55@tlpar.pekininsurance.com:8085@ @pinet.pekininsurance.us@pidev.pekininsurance.com@ @12.179.10.177@pidev.pekininsurance.com@ @pimodel.pekininsurance.us@pidev.pekininsurance.com@ @deviis01@pidev.pekininsurance.com@ @DEVIIS01@pidev.pekininsurance.com@ @test.pekininsurance.com:8085@tlpar.pekininsurance.com:8085@ @test.pekininsurance.com@tlpar.pekininsurance.com:8085@ @prod.pekininsurance.com:8085@tlpar.pekininsurance.com:8085@ @prod.pekininsurance.com@tlpar.pekininsurance.com:8085@}
            STREAM::enable
        }
    }
    
  • JimT02's avatar
    JimT02
    Icon for Nimbostratus rankNimbostratus

    Thanks. That worked.

     

    Any reason why this can't be done using the stream profile. Also, there should be no problem adding the log statements back in, should there.

     

    thanks again.

     

  • No problem re-adding the log statements.

     

    In generally, I don't care to use the STREAM profile directly. It's a brute force tool that works on ALL data in all directions. You clearly don't want to modify incoming data, and doing so could actually be detrimental to the application, so using STREAM logic in an iRule is a more precise alternative.

     

  • Your PDF files are corrupt or damaged and could not be repaired opening pdf file. In this condition, you can very well take help of Kernel for PDF Repair tool to repair or restore your all data from damaged PDF files. For more information, visit here: http://www.pdffilerepair.net