You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Integration libraries: okhttp3 same version (4.10.0)
Device/Android Version: any device
Issue details / Repro steps / Use case background:
Slightly related to this issue. I want to have a proper User Agent for Glide Requests. Because of untagged socket strict mode I added the okhttp integration to use an Interceptor to tag socket traffic, also this interceptor sets the User-Agent.
Upon notice that the User-Agent was not correct, I also checked our custom Loader and put a header in the GlideUrl I build. I confirmed by setting breakpoints, that the header there and in the okhttp-Interceptor is set.
Glide Version: 4.10.0
Integration libraries: okhttp3 same version (4.10.0)
Device/Android Version: any device
Issue details / Repro steps / Use case background:
Slightly related to this issue. I want to have a proper User Agent for Glide Requests. Because of untagged socket strict mode I added the okhttp integration to use an Interceptor to tag socket traffic, also this interceptor sets the User-Agent.
Upon notice that the User-Agent was not correct, I also checked our custom Loader and put a header in the GlideUrl I build. I confirmed by setting breakpoints, that the header there and in the okhttp-Interceptor is set.
Glide Module:
Relevant Loader method
default headers used:
Custom Glide URL object
User Agent is always:
User-Agent | okhttp/4.2.2
The text was updated successfully, but these errors were encountered: