I have a systems analyst who came to me with a problem with retrieving
a PDF file from a clients website. I've reduced the explaination to the
bare facts thus if you need more information just let me know.
The Setup:
- Initial request of the PDF file produces "Access Denied by security
policy"
- Using same browser instance minutes later, a refresh displays the PDF
file
- Using Squid proxy
The Evidence:
Failed attempt 1 with initiating socket connections through proxy:
Number Status URL
0 FIN,200 GET
http://client.domain.com/company/Sho...LINK=L73692528
1 FIN,200 GET
http://client.domain.com/company/Sho...PDFHeader.aspx
2 FIN,403 GET /Library/219/219323.pdf
3 FIN,403 GET http://client.domain.com/company/Images/319393/
Successful attempt 2, after initiating socket connections are
completely closed, through proxy.
**Same browser instance
Number Status URL
0 FIN,200 GET
http://client.domain.com/company/Sho...LINK=L73692528
1 FIN,200 GET
http://client.domain.com/company/Sho...PDFHeader.aspx
2 FIN,304 GET http://client.domain.com/company/219/219323.pdf
3 FIN,403 GET http://client.domain.com/company/Images/319393/
Side Note:
- If explicit access to client.domain.com via IP/proxy there is no
problem in the initial request
- If using Mozilla Firefox there is no problem in the initial request
- If the test machine uses Paros 3.2.13 there is no problem in the
initial request
- If the initial socket connections completely close and the user
refreshes the page the resource displays (see The Setup)
- IT Security has allowed unchallenged access to the clients domains
Questions:
1. Why would the initiating communication produce a failure but the
same browser instance making subsequent communication succeed?
2. Why is the initiating communication requesting
"/Library/219/219323.pdf" but the second requests
http://client.domain.com/company/219/219323.pdf?
3. Is there a resolution to this problem?
