A10 got a error http 301

Product Discussions ADC - Application Delivery
1

Someone has had this kind of inconvenience

I have the following topology

A10 → SW → SERVERS

I currently have 3 web servers, two of which are working normally, and have practically the same configuration as below.

This is the config for the server that is not working.

!
slb server server server-error 10.10.10.10
port 80 tcp
port 443 tcp
!
slb service-group SG-server-error tcp
member server-error 80
member server-error 443
!
slb virtual-server VIP-SERVER-ERROR 10.20.20. 20
port 80 http
source-nat auto
service-group SG-server-error
ng-waf
port 443 https
source-nat auto
service-group SG-server-error
template client-ssl cert-server-error-client
ng-waf

But when querying, I get a 301 error which means that I have a redirection loop

I have made changes in the A10 configuration, such as creating two different service groups for each port independently, ssl server certificates, aflex so that the redirection is done by the a10, and with all of them I get the same 301 error.

Have you ever had something similar happen?

2

Generally, the service-group members will have the same port number. What port do we want the Real Server to receive traffic on? Port 80 or port 443?

The default configuration will perform destination port translation, so with your configuration, as connections are round-robin load balanced, the connections will hit the Real Server on ports 80 and 443.

I suggest you make two service-groups one for port 80 and one for port 443, and bind the appropriate service-groups to the virtual port. If you are configuring SSL Offload, you would only use the port 80 service-group.

slb service-group SG-server-error-80 tcp
member server-error 80
slb service-group SG-server-error-443 tcp member server-error 443

3

Packet capture on Thunder or the Server will be helpful to understand the traffic flow and cause of the multiple redirects.

Also, can you share the aflex you are using for HTTP → HTTPS redirect.