This is an archived forum post. The information may be outdated. Contact us if you have any questions.

Save To PDF Link on Samsung Galaxy Tab 10.1 default browser

stamo wrote on 2012-05-25:
Hi, I'm trying "Save To PDF link" and I have the folowing problem. If I click my link on my desktop computer - everithing works fine, but if I use my Samsung Galaxy Tab, all i get is an HTML file with description of PDFCROWD services. I've tryed to change my UASTRING to several different options (including Desktop and iPhone). I also checked HTML_REFFERER and it was OK. So I couldn't think of anything else and I've decided to ask you. Thank you in advance.
support wrote on 2012-05-27:

the user agent string has no bearing on this. The "Save To PDF Link" requires that the browser sends the Referer HTTP header field.

You are saying that the Referer is ok, how did you check that? Please, click this link on your Samsung Galaxy Tab and paste the result here.

Also, please post the link to the web page you are trying to convert here.
stamo wrote on 2012-05-27:

This is the result of test link on my Galaxy tab:

Test site for RefControl


Here is the link to my test page:
It is perfectly working on my desktop computer, but not on my galaxy tab.
stamo wrote on 2012-05-27:
This is the result file on my Galaxy Tab
support wrote on 2012-05-27:
It seems that the browser actually sends two requests, one with the referer information followed immediately by the other without the referer field. Here is an excerpt from our logs:
[25/May/2012:05:02:23 -0400] "GET /url_to_pdf/ HTTP/1.1" 200 34422 "" "Mozilla/5.0 (Linux; U; Android 3.2; bg-bg; GT-P7500 Build/HTJ85B) AppleWebKit/534.13 (KHTML, like Gecko) Version/4.0 Safari/534.13"
[25/May/2012:05:02:23 -0400] "GET /url_to_pdf/ HTTP/1.1" 301 0 "-" "AndroidDownloadManager"

I'm not familiar with the Galaxy Tab but the link will not work unless you

  • either somehow force the AndroidDownloadManager to send the referer information,
  • or you manage to eliminate the second request entirely.

If you need a truly cross-browser solution you may want to try out our HTML to PDF API which does not rely on the referer information.
stamo wrote on 2012-05-27:
Thank you very much for your reply. I think I will try API, I just do not know how many tokens I need.
support wrote on 2012-05-28:
Ok, you can sign up for a free API test account here to see if the API fits your needs.