openresty / openresty/lua-nginx-module
openresty proxy_pass rewrite not with potree view
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 11.8k
- Forks
- 2.1k
- Avg merge
- 6h 1m
- Merged PRs (30d)
- 6
Description
I have openresty and node application openresty used to authenticate user using lua. here is my nginx.conf file.
When give location /potree app loading properly but when click on folders in its not opening
But when I use location / its working file. attached image for reference.
Here is nginx.conf file
`server {
listen 80 default_server;
listen 80;
listen [::]:80;
server_name localhost;
resolver 127.0.0.11 valid=1s;
set $session_check_ssi off;
access_by_lua '
local opts = {
My keycloak config
}
-- call introspect for OAuth 2.0 Bearer Access Token validation
local res, err = require("resty.openidc").authenticate(opts)
';
I disabled caching so the browser won't cache the site.
expires 0;
add_header Cache-Control private;
location /potree {
rewrite ^/potree(.*) /$1 break;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_pass http://potree:1234;
}
error_page 404 /404.html;
location = /40x.html {
}
redirect server error pages to the static page /50x.html
error_page 500 502 503 504 /50x.html;
location = /50x.html {
}
}`
Attached animated screen
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the nginx.conf shown in the issue, especially the /potree location, rewrite, and proxy_pass settings. Compare the browser requests and folder-navigation behavior under /potree with the working root location, then verify that Potree folder clicks load successfully through the proxied path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua, nginx, node.js
- Domain
- backend, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100