I tried to use securepages, but I was not able to upload files. Just leave empty the list of pages which will be secured, and file upload works as expected.

Comments

rblomme@drupal.org’s picture

rblomme@drupal.org commented

similar problem: http://drupal.org/node/76736

gordon’s picture

gordon commented
Status: Active » Fixed

This has been fixed by #82523 where the system will add the https to the page.

Also for the uploads you may want to add the page upload/js* to the secure pages.

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)
seanberto’s picture

seanberto commented
Version: 4.7.x-1.x-dev » 4.6.x-1.x-dev
Priority: Critical » Normal
Status: Closed (fixed) » Active

I'm running into the same issues as mentioned in node/76736, node/76735, and this issue - however, I'm running the Drupal 4.6 version of securepages. It doesn't look like fix #82523 referenced below was applied to the 4.6 module.

I tried the adding image_assist* and disknode* to the list of secure pages, but still get blank pop-ups when using these features with tinymce. I get the same when using the add link button on tinymce (though I'm not sure what the url for that pop-up is).

Any suggestions? I'll look into the 4.7 module code to see if I can port the $base_url fix.

Thanks,
sean

gordon’s picture

gordon commented
Status: Active » Closed (works as designed)

This is a configuration problem. You need to have the pages pointing to the same secure mode as the autocomplete links and the ajax links or the is security violations with the browser.

aaron1234nz’s picture

aaron1234nz commented

Just for the record, to get the file upload working in drupal 5 I needed three entries in the
"Pages which will be be secure: " box
node/*/edit
node/add*
upload/js*

this ensures all adding and editing content is done in secure mode

mstef’s picture

mstef commented

{edit out}

mandclu’s picture

mandclu commented

I was experiencing an HTTP 0 error every time I tried to upload an image into an imagefield. What was really puzzling me was that it worked fine on my main site, but my online store is in a separate subdomain and I got the error 100% of the time there.

After a big of digging I got wondering if the fact that the store is configured to do its edits via HTTPS might be the problem. A bit more digging brought me to this thread and got me thinking that maybe a tweak to the Secure Pages config would solve the issue.

Sure enough, all I had to do was add one line to the "Ignore Pages" field:
filefield/progress/*

Now the upload progress shows as expected. Just thought I'd report it here in case anyone having the same issue might benefit from the same fix.

carteriii’s picture

carteriii commented

mandclu, I realize it's been a long time since you left your message, but THANK YOU! I too was getting errors due to the filefield progress indicator. Adding filefield/progress/* to the ignore list solve the problem.