cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
591
Views
0
Helpful
5
Replies

L7 loadbalance content with special international language characters

770801tvdhaar
Level 1
Level 1

Hi, I'm trying to do layer 7 loadbalancing with webpages that have links with special language characters in the url, our ACE drops these ie. åöä

How to do?

class-map type http loadbalance match-any FB0111661

2 match http url .*

we running A1 code on our Ace

1 Accepted Solution

Accepted Solutions

We have seen this with all languages using non-ascii characters.

Your web browser should normally encode those characters as they are illegal per RFC.

Those characters have been allowed with the following ddts :

CSCsm89835: Accept not encoded characters after a ? inside url

Go to the latest A2(1.3) version or A3(2.1) if you have an appliance.

Gilles.

View solution in original post

5 Replies 5

You are probably hitting

CSCsh38439

Have you tried using different browsers?

Is the result same for all browsers.

I have seen that IE normally messes up with the special characters.

Syed

I don't know if this bug is affecting me, in the below example towards the end of the link it's that swedish language characters that gets dropped by ACE. Is anyone else experiencing something similar?

http://xxxx.xxxx.xxxxx/scripts/cgiip.exe/cm/pub/showdoc.p?docid=476&FolderId=7280&ObjectName=IT-råd

We have seen this with all languages using non-ascii characters.

Your web browser should normally encode those characters as they are illegal per RFC.

Those characters have been allowed with the following ddts :

CSCsm89835: Accept not encoded characters after a ? inside url

Go to the latest A2(1.3) version or A3(2.1) if you have an appliance.

Gilles.

Hi Gilles,

I have now upgraded to A2(2.0) and the problem with the static html pages went away, but now I have another problem with links from a webpage to pdf files that have both spaces and internationel characters in the file name?

Anyone else having the same problem?

I'd just like to add that the workaround for this was to do loadbalancing on layer 3 source addresses which is not very scalable

ie. class-map type http loadbalance match-any FBJACK

3 match source-address 10.0.0.0 255.252.0.0

4 match source-address 172.22.0.0 255.255.224.0