I have done a search through the issue queue, and couldn't find a similar posting to this, so my apologies if this is a duplicate.
When building sites for clients, we commonly use HTTP authorization on non-production sites (such as development, or staging sites) as a means of ensuring that these sites dont get picked up search engines, or that they aren't accessible to anyone other than ourselves and the client.
Currently with Entity Print 8.x-1.x, when testing on such a site the PDF generation fails with 401 Authorization Required error. This means any HTTP authorization has to be turned off to allow the PDF generation to be tested.
Would it be possible to add a 'develop' mode where by any auth details could be added to the settings page for the module?
This way, when PDF generation is tested on a site/server utilising HTTP authorization, these details could be taken into account to avoid the 401 error.
Comment | File | Size | Author |
---|---|---|---|
#6 | 2820401-6.patch | 7.36 KB | benjy |
#5 | 2820401-5.patch | 2.41 KB | benjy |
Comments
Comment #2
hiraethmarkbComment #3
benjy CreditAttribution: benjy commentedAre you using the wkhtmltopdf engine?
Comment #4
benjy CreditAttribution: benjy commentedI tested this quickly on 8.x-2.x but It worked as expected, any tips on how to reproduce this? What are you using to implement httpauth?
Comment #5
benjy CreditAttribution: benjy commentedI was able to reproduce this using apache's httpauth.
Comment #6
benjy CreditAttribution: benjy commentedAdded support for Dompdf as well.
Comment #7
benjy CreditAttribution: benjy at PreviousNext commentedCommitted.
Comment #10
hoporr CreditAttribution: hoporr commentedFollowup issue: https://www.drupal.org/node/2845215
Related issue: https://www.drupal.org/node/2845222
Comment #11
jeanne.morgan10 CreditAttribution: jeanne.morgan10 as a volunteer commentedGetting "Authorisation failed, are your resources behind HTTP authentication? Check the admin page to set credentials." When i try and use DOMPDF. The username and password on the config for entity print don't give any descriptive information on what to do to help and the patches are outdated.