Cookie Support

[shism2]

I haven't really used Glide yet. How do I set headers and use cookies?

[sjudd]

By default Glide uses Volley for its network operations. I don't have any specific experience setting headers and cookies, but it's definitely possible to setup Volley however you wish and pass in your own request queue or your own Request subclasses. You can also implement a relatively simple interface and use whatever networking stack you wish: http://bumptech.github.io/glide/docs/com/bumptech/glide/loader/stream/StreamLoader.html. For an example using volley, see https://github.com/bumptech/glide/blob/master/library/src/com/bumptech/glide/volley/VolleyStreamLoader.java.

Once you've defined that interface, you then need just one call to the Glide singleton to replace our default network stack with your own. If you're interested I can also give you some documentation or examples on how that works.

[shism2]

Can you please provide me with documentation and examples?

[sjudd]

For replacing the default network stack?

[shism2]

Well, could you show me an example of what I would have to do to modify the headers or cookies?

[sjudd]

As I mentioned before, I've never done it myself. However, it looks like all you need to do is override getHeaders() in the volley request to set whatever you would like. You could start with essentially a copy/paste of VolleyStreamLoader I linked above and then override getHeaders() in the Request inner class.

[shism2]

Ok, thank you.

[bpappin]

Both of those links are returning 404.

[TWiStErRob]

I'm not sure if these are the refactored classes, but look at:
https://github.com/bumptech/glide/tree/master/integration/volley/src/main/java/com/bumptech/glide/integration/volley

Stream*Loader

Also: https://github.com/bumptech/glide#volley
Maybe: http://bumptech.github.io/glide/javadocs/331/index.html?com/bumptech/glide/load/data/DataFetcher.html

[bpappin]

Yeah, just discovered I can't add volley to this project as an android library.

The simplest way I that I can think to do this, is something like the setDefaultOptions except it exposed the request prior to executing the HTTP call.
That would allow the user to modify the request and set headers or cookies as needed.