As discussed in https://www.drupal.org/node/2599326, but that (somewhat unrelated) issue was closed.

Autocomplete filter being forced to use `index.php?q=`URLs should be a configuration option.

Comments

cudevdev created an issue. See original summary.

mrdalesmith’s picture

mrdalesmith commented

Have just been hit by this after security updates to 7.43 with sites hosted on nginx and blocking direct access to index.php

moehac’s picture

moehac commented

This fixed it for me:
https://github.com/perusio/drupal-with-nginx/issues/241

cudevdev’s picture

cudevdev commented

This bug affects both entity reference autocomplete and views exposed form autocomplete.

David_Rothstein’s picture

David_Rothstein commented

See discussion in the original issue (#2599326: Autocomplete function fails when index.html exists - After upgrading to Drupal 7.39 and chaos tools 1.8 ) - it is not clear why blocking Drupal from accessing its own index.php file should be a supported configuration, or what purpose that serves exactly.

So unless there's some really good reason for that which hasn't been stated yet, the best solution is probably just to stop blocking index.php (as in the above-linked GitHub issue)...?

mustanggb’s picture

mustanggb commented

Just came searching for David_Rothstein's hook_url_outbound_alter() fix over in #2599326-49: Autocomplete function fails when index.html exists - After upgrading to Drupal 7.39 and chaos tools 1.8 .

When the project autocomplete input on https://www.drupal.org/project/issues spat out virtually the same error message, oh the irony.

Konstantin Komelin’s picture

Konstantin Komelin commented

I think denying direct access to index.php is not an enemy of security team but a friend because it serves the same goal as any security code fixes.

My sites became buggy in one day and I need to do something with that. Slow Apache is not an option for many people including me. So, you better help me to find a solution rather than arguing about its necessity.

I can allow access to index.php, but I cannot understand why such solution that leads to use of non-clean urls could be applied in 2016.

Konstantin Komelin’s picture

Konstantin Komelin commented

A friend of mine advised Autocomplete Delux https://www.drupal.org/project/autocomplete_deluxe Tested, it works fine.
Note: Do not forget to change your field widget type.

Version: 7.42 » 7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.

Status: Active » Closed (outdated)

Automatically closed because Drupal 7 security and bugfix support has ended as of 5 January 2025. If the issue verifiably applies to later versions, please reopen with details and update the version.