HTTP redirection not succeeding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2009 06:47 AM - edited 03-11-2019 08:48 AM
Here only what I'm receiving when using static NAT on PIX 501 6.3:
HTTP/1.1 400 Bad Request
Server: Microsoft-IIS/5.1
Date: Thu, 25 Jun 2009 14:37:37 GMT
Content-Type: text/html
Content-Length: 87
I'm using many static NATs and showing a correct result when showing (show xlate) also (show access-list).
Is it possible due of MTU on TCP packets? If yes, what command can change the TCP MTU? If not what's possible reason of the problem.
Regards,
Omar
- Labels:
-
NGFW Firewalls
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2009 07:11 AM
try with
mtu outside 1500
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2009 07:16 AM
It it possible also caused by the cache server? I'm receiving it rapidly.
I'm using a direct connection without a proxy, where it may be?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2009 07:20 AM
try with clear xlate and with clear local commands
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2009 07:26 AM
I don't think so, the translations are right and working fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2009 08:30 AM
Fixed now!
It wasn't a Cisco problem, just the because the costumer IIS was using port 82 rather than the default 80
Thanks for all of you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2009 08:01 AM
Don't see how this could be an MTU issue...
You've established a successful HTTP connection and are receiving a 400 response code from the destination server. This looks like an application layer issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2009 08:33 AM
I fixed the problem before seeing your reply, but you gave the more logical reason.
Many thanks,
