I was wondering on possible cause for filefield_sources Remote URL functionality. php5-curl is installed on server and functioning. When I input remote URL for file download, it starts process and displays progress bar. Although for short time, above progress bar, error is given, which dissapears in a while - file is kept uploded and provided with additional fields. The error says:

An HTTP error 404 ocurred ./filefield/remote/progresss/story/field_attachments/0

Where does filefield/remote/progress folders should be, as I could not find in ./sites/default/files one?

CommentFileSizeAuthor
#4 filefield_sources_remote_progress_access.patch505 bytesquicksketch
#2 filefield_soures_http_transfer_error.png147.03 KBjrstmartin

Comments

jrstmartin’s picture

jrstmartin commented

Did you find a solution to this? I'm in the same boat...

jrstmartin’s picture

jrstmartin commented
StatusFileSize
new filefield_soures_http_transfer_error.png147.03 KB

Right, I spent 2 days trying to resolve this and had to give up :/ I'd like to mention a few things to make this issue more clear:

  • I do not receive this error when using Upload, only Remote URL. I'm using PHP uploadprogress and it works great with Upload.
  • When using Remote URL, and clicking Transfer, a progress bar is shown for a couple seconds, but doesn't display any progress. Then it disappears and the error message appears:
An HTTP error 404 occurred.
/filefield/remote/progress/article/field_file_attachments/0
  • "article" is my content type. "file_attachments" is my cck field.
  • The error message continues to display as the remote file continues to transfer. The remote file completes successfully. Error goes away.
  • I tried "throbber" instead of progress bar, but same error.
  • I'm using Varnish, but if I turn it off and put Apache back on port 80, same error.
  • PHP settings are amped-up: memory_limit 256M, max_execution_time 120, upload_max_filesize 100M.
  • The relevant code appears to be in sources/remote.inc on line 100?:
'path' => 'filefield/remote/progress/' . $element['#type_name'] . '/' . $element['#field_name'] . '/' . $element['#delta'],

I read in the Filefield issue queue about similar issues, but none are the same or relevant. Any help would be greatly appreciated. Screenie also attached. Thanks...

budda’s picture

budda
Primary language English
Location Cheshire
commented

I had this problem.

It was caused by the filefield being on a user profile form which was shown at sign up time to anonymous users.
The catch was that anonymous users had no access to content on the site - thus no "access content" permission.

The path 'filefield/remote/progress/%/%/%' is restricted by 'access arguments' => array('access content'),.

Does your user role have 'access content' granted? Saying that - getting a 404 error would be wrong, you should be getting a 403 error if the above was the case. Hmm.

quicksketch’s picture

quicksketch
he/him
commented
Title: HTTP error 404. » HTTP error 404 on progress bar if user doesn't have "access content" permission
Category: support » bug
Status: Active » Fixed
StatusFileSize
new filefield_sources_remote_progress_access.patch505 bytes

For now let's just change the access check to be TRUE, always granting access. It doesn't do anything other than check a cache, so it's not a particularly dangerous file path.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

jrstmartin’s picture

jrstmartin commented

Works. Thanks Nate! :))