Develop Reference

NGINX URI With Period Proxy Pass Issue

So we have a setup where nginx is our reverse proxy that uses proxy_pass to apache tomcat in several locations. The issue we encountered is this:
If a URI contains a dot/period as a trailing value (e.g. http://example.com/sub/john-doe.), this is not properly forwarded to tomcat.
As per the access log in tomcat, "period" was excluded/removed from the URI path.
(http://example.com/sub/john-doe.). --> (http://192.168.1.10:8080/sub/john-doe)
Testing directly to tomcat via local access (http://192.168.1.10:8080/sub/john-doe.) works fine. The "period" was not removed.
What is the correct configuration for this in nginx?
TIA
nginx 1.19 (windows)
Common configuration
proxy_redirect off;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forward-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $http_host;
add_header X-XSS-Protection "1; mode=block";
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
client_max_body_size 4000M;
location /sub {
proxy_pass http://<ip>:8080/sub
}

remove project name prefix from spring redirect url

I use nginx reverse proxy to connect tomcat and nginx config is:
server {
listen 80;
listen [::]:80;
server_name magnet.s-m.local;
location / {
proxy_pass http://tomcat:8080/magnet/;
proxy_cookie_path /magnet /;
proxy_redirect off;
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-Host $server_name;
}
}
every this is ok but when I want to redirect user spring add project name to redirect path.
#RequestMapping(value = "/login",method = RequestMethod.POST)
public String loginCheck(HttpSession session, #RequestParam("username") String user, #RequestParam("password") String password){
session.setAttribute("username",user);
return "redirect:/home";
}
this code redirect to http://magnet.s-m.local/magnet/home but I want to redirect http://magnet.s-m.local/home
if I use RedirectView it's work nice but using redirect:/home is better because I can decide to redirect or load jsp file if login failed.

Try removing proxy_redirect and proxy_set_header Host parameters from your nginx configuration:
location / {
proxy_pass http://tomcat:8080/magnet/;
proxy_cookie_path /magnet /;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $server_name;
}
You also can specify the proxy_redirect more in detail, but it should be activated.

Spring, SockJS - error during WebSocket handshake: Unexpected response code 400

I have implemented BE application with WebSockets support using Spring Boot. I use SockJS in order to connect to my WebSocket endpoint and during the connection process I get a following error:
error during WebSocket handshake: Unexpected response code: 400
but then (as you can see at the image above) everything is working fine and websocket opened.
Right now I don't understand what can be a reason of this issue and how to fix it. Please help.
UPDATED
Thanks for the paweln1986 help I have fixed version issue with SockJS lib but the issue with Unexpected response code 400 still exists:
I also using nginx in front of Tomcat 8. This is my nginx config:
server {
listen 443 ssl;
server_name myserver.com;
ssl on;
location /api/ {
proxy_pass_header X-XSRF-TOKEN;
proxy_pass http://localhost:8081/api/;
proxy_set_header Origin "http://localhost:8081/api/";
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_http_version 1.1;
}
location /dashboard/ {
proxy_pass http://localhost:8081/dashboard/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
location /manager {
proxy_pass http://localhost:8081/manager/;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
location / {
root /srv/www/htdocs/myserver/;
index index.html index.htm;
}
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root /srv/www/htdocs/;
}
}

You have wrong version of SockJS.
On the browser side, applications can use the sockjs-client (version 1.0.x) that emulates the W3C WebSocket API
http://docs.spring.io/spring/docs/current/spring-framework-reference/html/websocket.html
You are missing two things under your /api/ section
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
https://www.nginx.com/blog/websocket-nginx/

This complication also occurs if you are using SSL with Amazon load balancers. The listener of the elb should have an entry of SSL(instead of HTTPS) with load balancer port as 443 and instance protocol as TCP with instance port as 80 (Don't forget to add certificate)
This will enable WebSocket traffic to pass through.
For detailed reference :
https://blog.jverkamp.com/2015/07/20/configuring-websockets-behind-an-aws-elb/

How do i deploy a Vaadin Spring server on a non-root URL

I am trying to deploy two instances of a Vaadin Spring application using nginx to redirect requests to the appropriate instance.
The first server should be available at www.example.org/, the second one at www.example.org/second/, both at port 80. The first server listens to port 9002, the second to port 9003.
My nginx configuration looks like this:
server_name www.example.org localhost;
root /;
location / {
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $host;
proxy_cookie_path ~*^/.* /;
proxy_pass http://127.0.0.1:9002/;
proxy_redirect off;
}
location /second/ {
proxy_set_header X-Forwarded-Host $host/second;
proxy_set_header X-Forwarded-Server $host/second;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $host/second;
proxy_cookie_path ~*^/.* /;
proxy_pass http://127.0.0.1:9003/;
proxy_redirect off;
}
}
The first server works completely fine.
I can also access the second server; requests to any of its URLs correctly redirect me to its login page. As soon as i click a button, i get a session expired message. From the nginx access logs, it looks like the button click triggers a POST request which goes to /vaadinServlet/UIDL/?v-uiId=0 and returns code 200 (OK).
I believe the request should really go to /second/vaadinServlet/UIDL/?v-uiId=0. Thus, i am stuck on the login page.
Am i correct in my assumption that the vaadinServlet request goes to the wrong URL? If so, how do i get it to go to the correct one?
I am thinking of using nginx to extract the necessary information from the referral URL but i believe it should be possible to configure Vaadin/Spring to handle this case.

Hide project name with nginx proxy

I try to redirect the traffic from the nginx proxy (PROXY_IP) to the Wildfly instance (WILDFLY_IP). The java project is reachable with the url http://WILDFLY_IP:8080/PROJECT_NAME. I want to hide the project name, that the users can access http://PROXY_IP/ and see the same. The nginx proxy is also used to enforce HTTPS.
My config looks like this:
server {
listen 80;
return 301 https://$host$request_uri;
}
server {
listen 443;
server_name PROXY_IP;
ssl_certificate xxxx;
ssl_certificate_key xxxx;
ssl on;
ssl_session_cache builtin:1000 shared:SSL:10m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4;
ssl_prefer_server_ciphers on;
access_log /var/log/nginx/proxy.access.log;
error_log /var/log/nginx/proxy.error.log;
location / {
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://WILDFLY_IP:8080/PROJECT_NAME;
proxy_read_timeout 90;
proxy_redirect http://WILDFLY_IP:8080/PROJECT_NAME https://PROXY_IP;
}
location /PROJECT_NAME {
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://WILDFLY_IP:8080/PROJECT_NAME;
proxy_read_timeout 90;
proxy_redirect http://WILDFLY_IP:8080/PROJECT_NAME https://PROXY_IP;
}
}
The configuration forwards the traffic to the Wildfly instance and enforce https, but it redirects the user from http://PROXY_IP/ to https://PROXY_IP/PROJECT_NAME

I think you can just do this with a rewrite.
location /PROJECT_NAME {
....
rewrite /PROJECT_NAME/(.*) /$1 break;
....
}