| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
changes to common libraries from the server codebase:
* Additional error checking in http handlers.
* Uniform log spam for http errors.
* Switch to using constants for http heads and status codes.
* Fixed bugs in incorrectly checking if parsing LLSD xml resulted in an error.
* Reduced spam regarding LLSD parsing errors in the default completedRaw http handler. It should not longer be necessary to short-circuit completedRaw to avoid spam.
* Ported over a few bug fixes from the server code.
* Switch mode http status codes to use S32 instead of U32.
* Ported LLSD::asStringRef from server code; avoids copying strings all over the place.
* Ported server change to LLSD::asBinary; this always returns a reference now instead of copying the entire binary blob.
* Ported server pretty notation format (and pretty binary format) to llsd serialization.
* The new LLCurl::Responder API no longer has two error handlers to choose from. Overriding the following methods have been deprecated:
** error - use httpFailure
** errorWithContent - use httpFailure
** result - use httpSuccess
** completed - use httpCompleted
** completedHeader - no longer necessary; call getResponseHeaders() from a completion method to obtain these headers.
* In order to 'catch' a completed http request, override one of these methods:
** httpSuccess - Called for any 2xx status code.
** httpFailure - Called for any non-2xx status code.
** httpComplete - Called for all status codes. Default implementation is to call either httpSuccess or httpFailure.
* It is recommended to keep these methods protected/private in order to avoid triggering of these methods without using a 'push' method (see below).
* Uniform error handling should followed whenever possible by calling a variant of this during httpFailure:
** llwarns << dumpResponse() << llendl;
* Be sure to include LOG_CLASS(your_class_name) in your class in order for the log entry to give more context.
* In order to 'push' a result into the responder, you should no longer call error, errorWithContent, result, or completed.
* Nor should you directly call httpSuccess/Failure/Completed (unless passing a message up to a parent class).
* Instead, you can set the internal content of a responder and trigger a corresponding method using the following methods:
** successResult - Sets results and calls httpSuccess
** failureResult - Sets results and calls httpFailure
** completedResult - Sets results and calls httpCompleted
* To obtain information about a the response from a reponder method, use the following getters:
** getStatus - HTTP status code
** getReason - Reason string
** getContent - Content (Parsed body LLSD)
** getResponseHeaders - Response Headers (LLSD map)
** getHTTPMethod - HTTP method of the request
** getURL - URL of the request
* It is still possible to override completeRaw if you want to manipulate data directly out of LLPumpIO.
* See indra/llmessage/llcurl.h for more information.
|
|
|
|
moved all parameters other than search query to base64 encoded llsd
|
|
produce search results if search window is already open
use new parameters when opening existing floater
|
|
viewer fail with intrusted browser error in viewer
|
|
search floater derives from floater_web_content
all web content now uses floater_web_content instead of media_browser
|
|
EXP-630 My appearance floater may be opened by SLApp
EXP-633 Search floater can be opened by SLApps
|
|
type detection
|
|
trusted content is now a const attribute of LLMediaCtrl, set in constructor params
|
|
back-out the back-out for this branch. yay.
|
|
Backing out this merge that I pushed (prematurely) to the wrong place.
|
|
|
|
|
|
|
|
We now tear down the web view when we close the find floater. This
means that we don't show the previous search results when performing a
new search. It also makes for more efficient use of resources as we
don't have a web view continually running in the background. (This is
how the Help Browser currently works too.)
|
|
Displays the search floater and performs a search. You can specify an
optional category and an optional search string. See the wiki docs for
usage details: https://wiki.lindenlab.com/wiki/Viewer_2.0_SLapps
|
|
When a new search is performed, we first display a blank page in the
search floater so that the previous results are not visible while the
new results are being retrieved from the search server.
|
|
Search and the Home sidetray now have their own specific
authentication keys that they support from login.cgi, but they
fallback to a common key as follows:
Search: "search_token", fallback to "auth_token"
Home: "home_sidetray_token", fallback to "auth_token"
|
|
The search URL is now specified in app_settings/settings.xml (instead
of in floater_search.xml), and it is now defined more flexibly with
support for various substitution strings, such as [QUERY], [AUTH_KEY],
[MATURITY], [GODLIKE], etc.
I pulled the common substitution code out into a new static method,
LLWeb::expandURLSubstitutions(). This provides support for common
strings like [VERSION], [CHANNEL], [LANGUAGE], [OS], etc. The Help and
Home sidetray code has been updated to use this new function, to avoid
replicating this behavior 3 times.
I also cleaned up the app_settings/settings.xml file and removed the
old search keys of: SearchURLDefault, SearchURLQuery, and
SearchURLSuffix2.
|
|
If you change your god level from when you performed a search, the
search results may be inappropriate for your god level (we pass the
current god status to the search web pages). When this is the case, we
now display a warning at the bottom of the search floater to let the
user know that they should redo their search.
|
|
The state of gAgent.isGodlike() is now passed through to the Search
web pages via a new g=[0|1] query parameter.
|
|
Added Back, Forward, and Home buttons to the web view for the Home
side panel. Still more work to do here, but the basic functionality
is there; albeit hardcoded to secondlife.com.
I notice that you can click Back on the first page. Seems to be an
issue for the general media browser too. I'll file a JIRA for that.
|
|
new ?lang=<LANG> query parameter.
|
|
Now preferred maturity is passed to the search web pages as an
r={13|21|42} query param.
|
|
The Search URL now includes a "r=" query parameter to specify the
user's preferred maturity rating. This can be "pg" or "pg,mature"
or "pg,mature,adult".
|
|
pass this token through to the search web pages via a q= query
parameter in the search URL. This will let the search facility
determine the user's maturity and teen settings.
I also now escape the search string that the user typed in, 'cos they
could type anything.
Thanks to Mani for showing me how to get responses from login.cgi.
|
|
URL that we send to the Search web page. This can be used to determine
the maturity levels to display. These bools are passed as query params
in the URL (as agreed upon with the search team).
|
|
You can now specify a search category for all web-based searches,
e.g., "all" (default), "people", "places", "events", "groups", "wiki",
"destinations", "classifieds". Specifying a category will add the
relevant subdir to the search URL, as specified by the search team.
|
|
This new Search floater replaces the current XUI-based search
interface with one that is implemented entirely as a web service.
This is currently pointing toward a temporary search URL. The URL will
be updated when the stable version is available.
|
