- Diviner Queries
- All Atoms
- Search
- Diviner Search
Diviner All Atoms
All Atoms
All Atoms
- src/aphront/response/Aphront400Response.php
- File
- Method
- Method
- Method
- src/aphront/response/AphrontPlainTextResponse.php
- File
- Method
- Method
- Method
- src/aphront/response/AphrontDialogResponse.php
- File
- Class
- Method
- Method
- Method
- Method
- Method
- src/aphront/response/AphrontJSONResponse.php
- File
- Responds to a request by proxying an HTTP future.
- Class
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- src/aphront/response/AphrontHTTPProxyResponse.php
- File
- An object can implement this interface to allow it to be returned directly from an @{class:AphrontController}.
- Interface
- Produce the equivalent @{class:AphrontResponse} for this object.
- Method
- src/aphront/interface/AphrontResponseProducerInterface.php
- File
- Class
- src/aphront/exception/AphrontException.php
- File
- These exceptions are raised when a client submits a malformed request.
- Class
- Method
- Method
- Method
- src/aphront/exception/AphrontMalformedRequestException.php
- File
- Class
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- src/aphront/AphrontController.php
- File
- Guard writes against CSRF. The Aphront structure takes care of most of this for you, you just need to call:
- Class
- Allow execution of unguarded writes. This is ONLY appropriate for use in script contexts or other contexts where you are guaranteed to never be vulnerable to CSRF concerns. Calling this method is EXTREMELY DANGEROUS if you do not understand the consequences.
- Method
- Declare that you have finished performing unguarded writes. You must call this exactly once for each call to @{method:beginUnguardedWrites}.
- Method
- Begin a block which permits unguarded writes. You should use this very sparingly, and only for things like logging where CSRF is not a concern.
- Method
- Enter a scope which permits unguarded writes. This works like @{method:beginUnguardedWrites} but returns an object which will end the unguarded write scope when its __destruct() method is called. This is useful to more easily handle exceptions correctly in unguarded write blocks:
- Method
- Declare intention to perform a write, validating that writes are allowed. You should call this method before executing a write whenever you implement a new storage engine where information can be permanently kept.
- Method
- Return on instance of AphrontWriteGuard if it's active, or null
- Method
- Determine if there is an active write guard.
- Method
- Dispose of the active write guard. You must call this method when you are done with a write guard. You do not normally need to call this yourself.
- Method
- Construct a new write guard for a request. Only one write guard may be active at a time. You must explicitly call @{method:dispose} when you are done with a write guard:
- Method
- src/aphront/writeguard/AphrontWriteGuard.php
- File
- Method
- src/aphront/writeguard/AphrontScopedUnguardedWriteCapability.php
- File
- Method
- Method
- Method
- Method
- Method
- src/applications/settings/editor/PhabricatorUserPreferencesEditor.php
- File
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method
- Method