Timeline for What is the purpose of "use curl --cookie with a file that doesn't exist"?
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 1, 2020 at 16:24 | comment | added | user313992 |
@SeligkeitIstInGott I've tried to clarify the answer a bit, and include the suggestion to use /dev/null instead of non-existing file, which may turn up to exist when you suspect it the less ;-)
|
|
| Apr 1, 2020 at 16:21 | history | edited | user313992 | CC BY-SA 4.0 |
IMHO
|
| Apr 1, 2020 at 16:16 | comment | added | SeligkeitIstInGott | It wasn't clear. I was just seeking a clarification. That's all I needed. Thanks. | |
| Apr 1, 2020 at 16:02 | comment | added | user313992 |
@SeligkeitIstInGott haven't I answered that above? "by not using any --cookie option, as I did in the second example". Not accepting cookies is the default AFAIK. Am I missing something?
|
|
| Apr 1, 2020 at 15:58 | comment | added | SeligkeitIstInGott | I second the question of how to make curl not accept cookies at all. Wget has the "--no-cookies" flag. Is there an equivalent in curl? Unless perhaps not accepting cookies is the default in curl. | |
| Jan 31, 2019 at 1:57 | comment | added | user313992 | If by "record" you mean copying the string somewhere so it could be sent back with subsequent requests, then, yes, you'll have to "record" it. The server doesn't know or care what you doing with it, as long as you're sending it back, so it could keep state and track you through multiple requests. This is already quite offtopic, but there's another method you could keep state in HTTP -- by encoding it in the url. The downside of that vs. cookies is that it's too obvious to the user ;-) | |
| Jan 30, 2019 at 23:59 | comment | added | user313992 |
1. -L is a case where curl does multiple requests in a single invocation; other case is where you're using curl with multiple urls. 2. by not using any --cookie option as I did in the 2nd example. "Accepting cookies" means sending them back in requests, in a Cookie: header.
|
|
| Jan 30, 2019 at 23:51 | comment | added | Tim | " if you don't accept their cookies". how can you make curl not accept cookies? | |
| Jan 30, 2019 at 23:45 | comment | added | Tim | Thanks. Is --cookie without a real file only used when you're using the -L option ("follow through 3XX redirects")? | |
| Jan 30, 2019 at 23:36 | vote | accept | Tim | ||
| Jan 30, 2019 at 22:56 | history | edited | user313992 | CC BY-SA 4.0 |
a maybe less awkward explanation
|
| Jan 30, 2019 at 22:47 | history | edited | user313992 | CC BY-SA 4.0 |
added 209 characters in body
|
| Jan 30, 2019 at 22:36 | history | answered | user313992 | CC BY-SA 4.0 |