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
It looks like the way to send a header for e.g. a session ID, is by setting option 6 to specify GET or POST. This is counter-intuitive if you're just sending a bunch of GETs and leaving the default. I'd recommend either something in the docs or making headers a separate option.
The text was updated successfully, but these errors were encountered:
I agree. I didn't write that part, it was generously contributed It's on
my list of things to clean up, but right now I'm low on free time to get
another release out the door. If you'd like to contribute it would be
greatly appreciated.
It looks like the way to send a header for e.g. a session ID, is by
setting option 6 to specify GET or POST. This is counter-intuitive if
you're just sending a bunch of GETs and leaving the default. I'd recommend
either something in the docs or making headers a separate option.
—
Reply to this email directly or view it on GitHub #36.
@darinrogers@tcstool Closing this issue as this appears to have been merged into master already. Please reply if you believe I have closed this in error.
It looks like the way to send a header for e.g. a session ID, is by setting option 6 to specify GET or POST. This is counter-intuitive if you're just sending a bunch of GETs and leaving the default. I'd recommend either something in the docs or making headers a separate option.
The text was updated successfully, but these errors were encountered: