Error 400 Bad request

Question

Hi, &nbsp;&nbsp;
I have a BIGIP LTM version 9.4.6 the problem is that i have a VIP listening in port 80 with two webservers and i can access correctly to http://www.myweb.com&nbsp;
But i have other VIP with the same ip listening in 443 with ssl client profile and when i try access to https://myweb.com the request load for a long time and then show a 400 error Bad request :&nbsp;
Your browser sent a request that this server could no understand. Reason: You're speaking plain HTTP to an SSL-enabled server port.&nbsp;
&nbsp;The webservers are listening in 80 and 443 because I test request that don't pass throught BIGIP and shows me the web correctly with the certificate loaded in the BIGIP.&nbsp;
&nbsp;Also i have tried to enable SNAT but doesn't work.&nbsp;
What could be the cause of the problem.&nbsp;&nbsp;

nathan_houck_65 · Answer

Have you tried using different browsers?

alejandro_3444 · Answer

Yes I have used firefox, IE and chrome 
&nbsp;  
&nbsp;  
&nbsp; regards.

chris_phillips · Answer

use firebug or chrome dev tools to look at your requests. You're definitely not trying to hit http://myweb.com:443??

alejandro_3444 · Answer

I know that the request is good because the browser shows me the certificate that I have loaded in the BIGIP but then the error appears.&nbsp;
 &nbsp;

hooleylist · Answer

Can you use curl to access the virtual server which triggers the 400 response?  I'd guess like Chris suggests that something is redirecting to an HTTPS URL with the port hard coded to 80 (You're speaking plain HTTP to an SSL-enabled server port). 
&nbsp;  
&nbsp; Here are examples for http and then https: 
&nbsp;  
&nbsp; curl -v http://1.1.1.1 
&nbsp;  
&nbsp; curl -vk https://1.1.1.1 
&nbsp;  
&nbsp; Aaron

Forum Discussion

Error 400 Bad request

7 Replies

Recent Discussions

F5Access | MacOS Sonoma

Active- Active HA setup

syslog server connection

Cannot see floating MAC address outside of ESXi

Rewrite uri translation not working

Related Content

Distributed caching of authentication requests with NGINX Ingress Controller

Logging DNS Requests

API REST error 400

Insufficient permissions BIG-IQ login error

F5 Logs API 400 error