Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7725845
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 1, 20262026-06-01T05:02:58+00:00 2026-06-01T05:02:58+00:00

I have the following in nginx: # backend location /backend/ { deny all; }

  • 0

I have the following in nginx:

# backend
location /backend/ {
    deny all;
}

rewrite ^/aaaa/([0-9]+)-([0-9]+)-([0-9]+)\.jpg$ /backend/u/$1/$2/$3.jpg last;
rewrite ^/bbbb/([0-9]+)-([0-9]+)\.json$ /backend/u/$1/$2/report.json last;

but unfortunatelly I get 403 for the 2 rewrites.

Here is the question, how can I serve these files from /backend/* through the rewrites but block anything else?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-01T05:03:00+00:00Added an answer on June 1, 2026 at 5:03 am

    Try this patch:

    location /backend/ {
    -    deny all;
    +    internal;
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have the following location directive in my nginx config file: server{ ... location
I have following script that executes all the .reg files in the current directory.
I have following CSS: table tbody tr:last-child td { padding-top: 7px; border-bottom: 0; }
I'd like to do an Nginx rewrite where I have two domains: domain.com and
I have NGINX running on port 8080. I have the following setup in my
I have the following error in the nginx logs: 2011/12/16 13:52:30 [error] 7490#0: *1000
I have the following setup: NGINX -> Apache -> PHP scripts Apache is serving
I have the following nginx configuration fragment: server { listen 80; server_name mydomain.io; root
I have the following apache rewrite rule: RewriteEngine On RewriteRule ^id/([^/\.]+)$ item.php?id=$1 [L] and
I have following plist: <?xml version=1.0 encoding=UTF-8?> <!DOCTYPE plist PUBLIC -//Apple//DTD PLIST 1.0//EN http://www.apple.com/DTDs/PropertyList-1.0.dtd>

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.