header endocing

[Jack Wistering]

what is the encoding Bluecoat uses for the custom headers (x-authenticated-user, xff headers..etc..) to send an upstream proxy?

[Jacob Miles]

Hi Jack,

Are you asking about the character encoding? like UTF8?

Thanks!

[Jack Wistering]

Yes Jacob. what is the character encoding, and how to change the encoding?

For example:
Text encoding – utf-8, utf-16
Binary Encoding – Base64, Base 128, or no encoding

I don't see any option available on UI, is it doable through CPL?

[Slava]

Hello Jack, 

I may not be able to provide you with what encoding is being used at this time, but see bellow a method you can use via the CPL policy to encode the cleat text XFF Header that proxy sends upstream in to a base64 encoding, base128 not an option yet.
Copy and paste as is in to your local policy file or in to a CPL Layer in the VPM.

;===========START Encode all XFF in base64==========

define action Encode_All_XFF
set(request.header.x-forwarded-for, "$(x-client-ip:encode_base64)")
end

<Proxy>
action.Encode_All_XFF(yes)

;===========END Encode all XFF in base64==========

The same principal can be applied to any header proxy can inject in to upstream request.
Please the see the CPL Guide for more info: https://techdocs.broadcom.com/content/dam/broadcom/techdocs/symantec-security-software/web-and-network-security/proxysg/7-2/generated-pdfs/CPL72.pdf

I hope this helps.
Slava

[Jack Wistering]

thanks Slava