Hi,
On Sun, Oct 09, 2022 at 10:13:32AM +0200, Gert Doering wrote:
> This patch was still sitting "unanswered" in the list archives (though
> it never landed in patchwork, as far as I can see).
*sigh*
More coffee on a sunday morning, it seems - this was actually merged
just fine, just never
Hi,
On Sat, Feb 25, 2017 at 08:40:14AM +0800, Antonio Quartulli wrote:
> When the auth-token option is pushed from the server to the client,
> the latter has to ignore the auth-nocache directive (if specified).
>
> The password will now be substituted by the unique token, therefore
> it can't be
Am 25.02.17 um 14:10 schrieb David Sommerseth:
> On 25/02/17 10:19, Gert Doering wrote:
>> Hi,
>>
>> On Sat, Feb 25, 2017 at 08:40:14AM +0800, Antonio Quartulli wrote:
>>> When the auth-token option is pushed from the server to the client,
>>> the latter has to ignore the auth-nocache directive
On 25/02/17 10:19, Gert Doering wrote:
> Hi,
>
> On Sat, Feb 25, 2017 at 08:40:14AM +0800, Antonio Quartulli wrote:
>> When the auth-token option is pushed from the server to the client,
>> the latter has to ignore the auth-nocache directive (if specified).
>>
>> The password will now be
Hi,
On Sat, Feb 25, 2017 at 08:40:14AM +0800, Antonio Quartulli wrote:
> When the auth-token option is pushed from the server to the client,
> the latter has to ignore the auth-nocache directive (if specified).
>
> The password will now be substituted by the unique token, therefore
> it can't be
