Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is working fine for me. </p> <pre><code>curl -L -c trackcookie.txt -d 'userCredentialsForm.userCredentials.email=flesk@gmail.com&amp;userCredentialsForm.userCredentials.password=flesk&amp;_target1=Login' https://www.sportstracklive.com/signin &gt; track.html </code></pre> <p>If you want any other page after you log in, you have to use <code>-b trackcookie.txt</code>:</p> <pre><code>curl -L -b trackcookie.txt https://www.sportstracklive.com/user/pepelu &gt; pepelu.html </code></pre> <p>You always need the <code>-L</code> option to log on to pages with cookie based authentication, because a cookie needs to be sent as part of the headers before any html, so it needs to redirect. The exception is cookies written by javascript, but that's another chapter.</p> <p><strong>EDIT:</strong> You're right. I wasn't logged in after all. The correct way to log in is:</p> <pre><code>curl -Lc trackcookie.txt http://www.sportstracklive.com/ &gt; /dev/null curl -Lb trackcookie.txt -d 'userCredentialsForm.userCredentials.email=flesk@gmail.com&amp;userCredentialsForm.userCredentials.password=flesk&amp;_target1=Login' https://www.sportstracklive.com/signin &gt; /dev/null curl -Lb trackcookie.txt http://www.sportstracklive.com/live/track/gpx?userid=31746 &gt; mytracks.zip </code></pre> <p>The cookie actually lives on after you log out, so it seems like it's this sequence of server requests that determines whether the session id in the cookie corresponds to a valid session or not. I figured that out after I got to download the zip file with curl using the same session id set in Firefox when I was logged in there, but only then.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload