0 Replies Latest reply on Nov 13, 2008 1:00 PM by eirirlar

    Possible bug with itext security on IE6

    eirirlar Newbie

      Hi,


      I'm encountering a problem with seam pdf and security on IE6. I am using Seam-2.1.0.SP1 and have a deployment on Tomcat with security defined in web.xml. I have basically copied the setup in the seam-itext example.


      The pdf-generation works fine until I define a security-constraint in web.xml like this:



      <security-constraint>
        <web-resource-collection>
          <web-resource-name>name</web-resource-name>
          <url-pattern>/*</url-pattern>
        </web-resource-collection>
      </security-constraint>



      After this, the pdf-generation in IE6 generates the following error message once I try to view the pdf:


      Cannot download ...pdf?docId=1&conversationId=7 from localhost



      (the error message might look different on an English browser as this was translated from Norwegian)


      On Firefox, the pdf is shown as you would expect.


      I've pinpointed the error more accurately. As it turns out, it is this specific constraint that causes the problem:


      <security-constraint>
        <web-resource-collection>
          <web-resource-name>name</web-resource-name>
          <url-pattern>*.xhtml</url-pattern>
        </web-resource-collection>
      </security-constraint>



      Although this works fine:


      <security-constraint>
        <web-resource-collection>
          <web-resource-name>name</web-resource-name>
          <url-pattern>*.jsf</url-pattern>
        </web-resource-collection>
      </security-constraint>



      Although allowing unsecured access to *.xhtml is not acceptable for the webapp I'm creating.


      Is this a bug or a feature? Is there any way I can work around it, that is securing both .jsf and .xhtml while having pdf generation work?


      Regards,


      Eirik


      Is this a bug or is it how it's supposed to be? Is there any way I can work around it, that is, securing both *.jsf and *.xhtml while having pdf generation work?


      Regards,


      Eirik