Laravel 5.6无法导入CSS文件：已尝试多种引入方式均无效

Hey there, let's work through this CSS loading problem step by step. You've already tried the standard asset helpers, so we'll dig into the less obvious causes here:

1. First, Confirm the Basics #

• Double-check file existence & path: Make sure public/css/style.css actually exists, and watch for case sensitivity (Linux servers care if it's Style.css vs style.css).
• Test direct access: Try visiting your-domain.com/css/style.css in your browser. If you get a 404, the issue is with your server/file setup—not Laravel's asset helpers.

2. Fix File Permissions #

Linux-based servers often block access to files with incorrect permissions. Run these commands from your project root:

chmod -R 755 public/css
chmod 644 public/css/style.css

For local environments like WAMP/XAMPP, ensure the server user (e.g., www-data on Apache) has read access to the public/css directory.

3. Repair Your .htaccess File #

Your provided .htaccess snippet is incomplete. Replace your public directory's .htaccess with the full Laravel default version—this ensures static files are served correctly:

<IfModule mod_rewrite.c>
    <IfModule mod_negotiation.c>
        Options -MultiViews -Indexes
    </IfModule>

    RewriteEngine On

    # Handle Authorization Header
    RewriteCond %{HTTP:Authorization} .
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # Redirect Trailing Slashes If Not A Folder...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_URI} (.+)/$
    RewriteRule ^ %1 [L,R=301]

    # Send Requests To Front Controller...
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteRule ^ index.php [L]
</IfModule>

Note: If you're on shared hosting, ensure your root .htaccess (outside public) points to the public directory correctly.

4. Clear All Caches #

Old cache can break asset URL generation. Run these commands in your terminal:

php artisan cache:clear
php artisan config:clear
php artisan view:clear

Also clear your browser's hard cache (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac)—browsers often cache failed 404 responses.

5. Check for Route Conflicts #

If you have a route like Route::get('/css/{file}', ...) in routes/web.php, it will intercept requests to your CSS file and route them to a controller instead. Delete or modify any routes that match static asset paths.

6. Verify Server Configuration #

• Apache: Ensure the mod_rewrite module is enabled. You can confirm this via phpinfo() or by contacting your host.
• Nginx: Make sure your server config points to the public directory as the root, and includes rules to serve static files:

  location / {
      try_files $uri $uri/ /index.php?$query_string;
  }
  
  location ~* \.(css|js|png|jpg)$ {
      expires 1y;
      add_header Cache-Control "public, immutable";
  }
  

Start with the direct URL test—it's the fastest way to narrow down whether the issue is with Laravel or your server/file setup.

内容的提问来源于stack exchange，提问作者JGeorgeJ