nuster
nuster copied to clipboard
CORS
Hi this is very basic question but i spent a lot of time but no success, im using nuster as a cache server and need to add CORS, below is my simplest config file
global
nuster cache on dir /cache
nuster manager on uri /internal/nuster purge-method PURGEX
frontend fe
bind *:443 ssl crt /cert.pem alpn h2,http/1.1
mode http
default_backend be
backend be
mode httpde
nuster cache on
nuster rule all disk on ttl 7d
server s1 1.1.1.1:80
i tried to add CORS
http-response set-header Access-Control-Allow-Origin "yourhostname.com"
but no success
any idea plz?
@SilipTv5
mode httpde
mode http I suppose
Did you put http-response set-header Access-Control-Allow-Origin "yourhostname.com"
in the config?
It should response with this header, what do you mean no success? No Access-Control-Allow-Origin header?
Thank you so much for a very quick response, so my config file should be look like this with CORS,
global
nuster cache on dir /cache
nuster manager on uri /internal/nuster purge-method PURGEX
frontend fe
bind *:443 ssl crt /cert.pem alpn h2,http/1.1
mode http
default_backend be
backend be
mode http
http-response set-header Access-Control-Allow-Origin "yourhostname.com"
nuster cache on
nuster rule all disk on ttl 7d
server s1 1.1.1.1:80
Right?
Yes
I thought with above config cache will save on nuster server for 7 days, but in reality it is not saving anything, its only playing video from backend server like a proxy server, where im doing wrong? i want that nuster server save video in cache from first request and serve for next 7 days, Thanks
@SilipTv5 The config is OK. Do you have permission to write to /cache ? Can you enable log and upload the logs?
if i want to use Nuster as a reverse proxy without using any cache, below config is ok?
global nuster manager on uri /internal/nuster purge-method PURGEX frontend fe bind *:443 ssl crt /cert.pem alpn h2,http/1.1 mode http default_backend be backend be mode http server s1 1.1.1.1:80
Yes
this is working and now facing SSL issue, any idea?
sounds like standard ssl termination, so this should help: https://www.haproxy.com/blog/haproxy-ssl-termination/
global
nuster cache on dir /cache
nuster manager on uri /internal/nuster purge-method PURGEX
frontend fe
bind *:443 ssl crt /cert.pem alpn h2,http/1.1
mode http
default_backend ssl_443
backend ssl_443
mode http
nuster cache off
nuster rule all disk on ttl 7d
server s1 00.00.00.00:443 ssl verify none
Finally this config work with SSL, but facing a minor issue, WordPress site health have this issue The REST API call gave the following unexpected result: (520) that is most probably is with SSL misconfiguration Any Help? Thanks