On 2022-01-21 13:17, Harriet Bazley wrote:
On 21 Jan 2022 as I do recall,
Jeremy Nicoll - ml netsurf wrote:
Also, the form when used on a webpage, sets variable
"user_remember_me"
and (I'm not completely sure) maybe also the submit button part sets
something - I don't know why it d
>> there might be hidden input fields, [...]
> Ah - I think I may have spotted something. The actual tag at
> the start contains an 'authenticity token':
[reformatted for readability]
>accept-charset="UTF-8" method="post">
>
> value="VfGGu3jwjsf6xNQmlmuu3Qkgc1BsZzgu0ikhluwq
On 21 Jan 2022 as I do recall,
Michael Drake wrote:
>
> On 21/01/2022 13:17, Harriet Bazley wrote:
>
> > Then the browser history getting updated with the new page and a
> > FETCH_REDIRECT from the login page to the user home page. No record of
> > what data was sent to the server,
On 21 Jan 2022 as I do recall,
Mouse wrote:
> > I'm afraid I don't know enough about HTML forms to understand exactly
> > what the Submit button is doing,
>
> HTML forms, I think, just generate a POST when submitting. But just
> prompting for two visible inputs doesn't mean there are
On 21/01/2022 13:17, Harriet Bazley wrote:
> Then the browser history getting updated with the new page and a
> FETCH_REDIRECT from the login page to the user home page. No record of
> what data was sent to the server, that I can see.
In your Choices file, try setting:
suppress_curl_debug:0
> I'm afraid I don't know enough about HTML forms to understand exactly
> what the Submit button is doing,
HTML forms, I think, just generate a POST when submitting. But just
prompting for two visible inputs doesn't mean there are only two
input fields in the POST; there might be hidden input fie
On 21 Jan 2022 as I do recall,
Jeremy Nicoll - ml netsurf wrote:
> On 2022-01-21 00:55, Harriet Bazley wrote:
>
> > I also tried using --post-data 'user-Login=USER&user_password=PASSWORD'
> > with no result,
>
> That /may/ be because you weren't careful enough coding that. According
>
On 2022-01-21 00:55, Harriet Bazley wrote:
I also tried using --post-data 'user-Login=USER&user_password=PASSWORD'
with no result,
That /may/ be because you weren't careful enough coding that. According
to the form code, the login variable isn't called "user-Login" but
instead (2 differences)
On 20 Jan 2022 as I do recall,
Harriet Bazley wrote:
> On 20 Jan 2022 as I do recall,
> simon_sm...@zen.co.uk wrote:
>
> [snip]
>
> >
> > The cookie part is probably a red herring. The conventional approach
> > would be to use the wget tools to fetch the login page and send
On 20 Jan 2022 as I do recall,
simon_sm...@zen.co.uk wrote:
[snip]
>
> The cookie part is probably a red herring. The conventional approach
> would be to use the wget tools to fetch the login page and send
> username and password using the features wget has built-in. Hey
> presto, now y
On 2022-01-20 06:46 PM, "Harriet Bazley" wrote:
> On 20 Jan 2022 as I do recall,
> cj wrote:
>
> > In article <88ea7bad59.harr...@bazleyfamily.co.uk>,
> >Harriet Bazley wrote:
> > > How can I use Netsurf's cookie file with wget to retrieve a web page
> > > that is only accessible
On 20 Jan 2022 as I do recall,
cj wrote:
> In article <88ea7bad59.harr...@bazleyfamily.co.uk>,
>Harriet Bazley wrote:
> > How can I use Netsurf's cookie file with wget to retrieve a web page
> > that is only accessible to logged-in users
>
> wget --help shows there are commands to
In article <88ea7bad59.harr...@bazleyfamily.co.uk>,
Harriet Bazley wrote:
> How can I use Netsurf's cookie file with wget to retrieve a web page
> that is only accessible to logged-in users
wget --help shows there are commands to send user names and passwords
when downloading, ftping etc. Have
13 matches
Mail list logo
