HI there,
I got an error 400 after processing the export on my server..
this is the url I end with the error:

On my local machine I end with this url:


What could be the reason for this?

#6 support-arguments-1210930-6.patch1.4 KBMatir
Members fund testing for the Drupal project. Drupal Association Learn more


Apfel007’s picture

found the reason .. the "%" is the problem .. how to get rid of this?
the same for the download path..
this is on part where the path is build .. simple cutting the wildcards in path ? Or better replace the wildcards?

function render_complete() {
    $return_path = empty($_GET['return-url']) ? '' : $_GET['return-url'];

    return theme('views_data_export_complete_page', url($this->get_option('path'), array('query' => 'download=1&eid=' . $this->batched_execution_state->eid)), $this->errors, $return_path);
Apfel007’s picture

Title: Error 400 » HTTP Error 400 Bad request

how to replace alle % in the pathes ? Witch functions create that pathes?

Apfel007’s picture

Title: HTTP Error 400 Bad request » %25 in URL causes a HTTP Error 400 Bad request

is this a apache 2.2 problem?

Little Miss Cinderella’s picture

I was re-decorating my blogger  .. then I got the 'Bad Request Error 400' ..   I re-formatted my computer, reloaded all .. I can now access my Blogger sites .. Don't know what the problem was, but I solved it by reloading my computer to Out-of-Box condition, and all is perfect now  :) ..I have an alert set up for this Error 400 .. Masses of people are having problems daily ..

Steven Jones’s picture

Title: %25 in URL causes a HTTP Error 400 Bad request » Replace wildcards in the views path
Version: 6.x-2.0-beta5 » 7.x-3.x-dev

We really should support views wildcards, so lets check this one out.

Matir’s picture

Status: Active » Needs review
1.4 KB

This patch uses views get_url() function to determine the path to use for the next steps. I've tested with a view with arguments (which inspired work on this) and it works for me. Testing would be appreciated.

(The patch can be applied via 'git am'.)

derhasi’s picture

Status: Needs review » Reviewed & tested by the community

I had a similar problem, with a path node/%/content/export. This patch solved it.

So, works fine!

Steven Jones’s picture

Status: Reviewed & tested by the community » Fixed

Thanks, pushed to all branches.

Status: Fixed » Closed (fixed)

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