Score:0

Apache's mod_speling works for GET requests, not for POST

cn flag

My setup:

  • Raspberry Pi 4 Model B Rev 1.4, 8 GB version

  • Raspbian 10 / buster, kernel version 5.10.17-v7l+

  • Apache 2.4.38

  • mod_speling enabled with a2enmod

  • the following lines in the configuration file of my site:

    CheckSpelling On
    CheckCaseOnly On
    
  • a simple index.php file in the root of my website.

GET calls (via a browser or curl) to both https://www.example.com/index.php and https://www.example.com/Index.php work. A POST call to https://www.example.com/index.php works too, but to https://www.example.com/Index.php it 404s:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
<hr>
<address>Apache/2.4.38 (Raspbian) Server at www.example.com Port 443</address>
</body></html>

What is going on here? Is mod_speling only supposed to work on GET calls? The documentation does not seem to indicate so.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.