top | item 37983913 (no title) slivanes | 2 years ago I think mostly because it’s less efficient byte transfer size, roughly +25%, and also it won’t be downloaded as an image in parallel. discuss order hn newest wingi|2 years ago Gzip will fix this problem. But these ebessed imgaes are not cache-able. neallindsay|2 years ago Gzip or Brotli will help, but the result will still be bigger when base64 is in the middle. Sohcahtoa82|2 years ago The only problem with using any sort of compression in HTTP is that unless you add extra countermeasures, you open your page up to the BREACH vulnerability:https://en.wikipedia.org/wiki/BREACH ulrischa|2 years ago That is a point
wingi|2 years ago Gzip will fix this problem. But these ebessed imgaes are not cache-able. neallindsay|2 years ago Gzip or Brotli will help, but the result will still be bigger when base64 is in the middle. Sohcahtoa82|2 years ago The only problem with using any sort of compression in HTTP is that unless you add extra countermeasures, you open your page up to the BREACH vulnerability:https://en.wikipedia.org/wiki/BREACH
neallindsay|2 years ago Gzip or Brotli will help, but the result will still be bigger when base64 is in the middle.
Sohcahtoa82|2 years ago The only problem with using any sort of compression in HTTP is that unless you add extra countermeasures, you open your page up to the BREACH vulnerability:https://en.wikipedia.org/wiki/BREACH
wingi|2 years ago
neallindsay|2 years ago
Sohcahtoa82|2 years ago
https://en.wikipedia.org/wiki/BREACH
ulrischa|2 years ago