CSG C5(14) alters HTTP traffic if http accounting is enabled

[tortoricir]

Hi guys,

I'm facing an issue with some mobile handsets that connect to the internet to gather information from the vendor website (http tcp 80).

I have CSG 5.5(14) configured in this way:

!

ip csg policy HTTP

accounting type http customer-string INTERNET

!

ip csg content WWW

ip any tcp 80

replicate

vlan CLIENTVLAN

policy HTTP

inservice

!

Mobile handsets receive an error while trying to connect.

A trace (attached) shows an HTTP 502 (Bad Gateway).

If I create a more specific content without policy (and consequently without http accounting) like the following, everything works:

!

ip csg content MYCONTENT

ip 84.0.0.0 255.0.0.0 tcp 80

replicate

vlan CLIENTVLAN

inservice

!

My problem is that the DNS resolves that hostname each time with different IP address in different subnets, so I don't have a safe way to map the webserver to this new content.

My questions:

Is there any method to safely map that destination without involving an huge amount of IP address that should match WWW content instead?

Anyone knows what is the behavior of http accounting in CSG?

Thanks in advance.

Regards,

Riccardo

[thomas.chen]

Each HTTP method must be initiated by the same endpoint that initiated the TCP connection.The CSG supports IP fragmentation for HTTP; Internet Message Application Protocol, version 4 (IMAP4); Post Office Protocol version 3 (POP3); Simple Mail Transfer Protocol (SMTP); Wireless Application Protocol (WAP) 2.0; and WAP 1.x, regardless of the order in which the flows arrive.Refer http://cisco.com/en/US/products/sw/wirelssw/ps779/products_configuration_guide_chapter09186a00806ab79a.html

[tortoricir]

Yeah, of course.

What is actually going on seems to be related to Out-Of-Order segments coming from the mobile handset.

What the TAC is going to investigate is why without http accounting everything works.

Regs,

Ric

[tortoricir]

Just for your information.

I'm facing this behavior with CSG 6.7 as well.

As far as I know CSG rel7x has a buffer in the server vlan, so OOO should be managed better.

Regs,

Ric