So what does this mean if I am using an encrypted SSL connection that is correctly configured? Is this kind of problem not already dealt with for me by the sec

So what does this mean if I am using an encrypted SSL connection that is correctly configured? Is this kind of problem not already dealt with for me by the secure transport layer? It would be a shame if the abstraction were leaky. My understanding of the contract is that whatever bits I supply will be securely transported within the limits of the configuration I have selected. If I pick a bad configuration then yes shame on me, but a good configuration won't care if I compress right?