Bug ID 558969: Optimization to JPEG-XR fails on Edge browsers

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP AAM(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,,, 13.1.4,, 13.1.5,, 14.0.0,,,,,, 14.0.1,

Opened: Nov 18, 2015
Severity: 3-Major


When image optimization to convert to JPEG-XR is enabled and an Edge client connects to BIG-IP it doesn't receive optimized image according to configured policy and DB variable ccdb.allow.edge.jpegxr set to "true".


JPEG-XR is expected to consume less throughput which may affect pages with multiple images rendering on it.


BIG-IP has AAM provisioned and a policy with image optimization to convert to JPEG-XR option enabled is attached to a virtual. An Edge client connects via this virtual.



Fix Information


Behavior Change