See the discussion here: https://caddy.community/t/v2-http-handlers-templates-functions-in-file-server-browse-template/9214

The file_server directive has a browse option which enables a directory index to be served when a directory is requested. By default, this index is rendered using a template which can be [found in the cod

OS/Environment

None yet, but I'm working on OS X v10.11.6 'El Capitan' client-side. (See 'The way of deployment (cloud or local)' below for details on considered server infrastructure.)

Ansible version

None yet, as I haven't yet gotten that far into setting up Algo.

Version of components from requirements.txt

Not applicable (see above.)

Summary of the pro

Currently we use both, but it's probably wrong:

radare2 on  master [$?] 
[i] ℤ rg __WINDOWS__ | wc -l                                                                                                                                                                                                       17:44:21 
377
radare2 on  master [$?] 
[i] ℤ rg _MSC_VER | wc -l                        

At least in the latest spec: https://openid.net/specs/openid-connect-rpinitiated-1_0.html

Currently Hydra uses id_token_hint to determine if logout is RP-initiated or OP-initiated. I do not think this is possible by relaying on id_token_hint.

Looking at the implementation of issueLogoutVerifier I think the logic is correct (if id_token_hint is missing, you ask for consent, if it is p

Not exactly a bug, for for those who have been using Claimable in earlier versions of OZ (for the purpose of transferOwnership followed by claimOwnership) - what are the options in v2.0.0?

Relying solely on Ownable.transferOwnership lacks a safety mechanism for accidentally transferring the ownership to an incorrect address.

At present, the only alternative that I see is copying `Cla