Skip to main content
L
lfred150
Participating Frequently
February 22, 2012
Answered

cfcontent and pdf with a destination

  • February 22, 2012
  • 2 replies
  • 706 views

I am trying to use the cfcontent string and the pdf I have also includes a Acrobat destination..when I enter the destination

test.pdf#4

it errors out..

Due to cf statements, I then enter

test.pdf##4

and then it says in the cfcontent error message

file not found

Is there a way to include this type of filename?

Leo

This topic has been closed for replies.
Correct answer Adam Cameron.

If you have a code question, it's always helpful to include your actual code, rather than describe it.

One thing you should bear in mind is that the FILE attribute of <cfcontent> references a file (on your file system), not a URI.  So it's inappropriate to include URI-specific elements in that value.

The fragment part of a URI (the bit after the #) is only relevant ot he browser, so to hit that fragment, it needs to be in the address the browser requested.  It's nothing to do with what you send back (you just send back the document).

You coudl conceivably use <cfheader> to tell the browser to fetch the URI with the fragment, and then from that URI return the PDF file.  The browser should then - if it suuprts PDF fragments - work out what to do.

--

Adam

2 replies

L
lfred150Author
Participating Frequently
February 22, 2012

Thanks for the feedback Adam..you have answered my question..did not make the correlation with the brower request vs file request.

Will also include code in the future.

Leo

A
Adam Cameron.Correct answer
Inspiring
February 22, 2012

If you have a code question, it's always helpful to include your actual code, rather than describe it.

One thing you should bear in mind is that the FILE attribute of <cfcontent> references a file (on your file system), not a URI.  So it's inappropriate to include URI-specific elements in that value.

The fragment part of a URI (the bit after the #) is only relevant ot he browser, so to hit that fragment, it needs to be in the address the browser requested.  It's nothing to do with what you send back (you just send back the document).

You coudl conceivably use <cfheader> to tell the browser to fetch the URI with the fragment, and then from that URI return the PDF file.  The browser should then - if it suuprts PDF fragments - work out what to do.

--

Adam

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices