Как загрузить страницу в WebView с куками?
Есть ссылка на определенную страницу (https://. ), которую надо отобразить в WebView. Сайт с авторизацией, авторизационные куки есть (их отдает веб сервис). Но вместо загрузки нужной страницы постоянно получаю отлуп на страницу ввода логина.
Пробовал по всякому, ничего не помогло.
где cookies — авторизационные куки.
На счет второго варианта иллюзий не питал, в документации ясно сказано: Note that if this map contains any of the headers that are set by default by this WebView, such as those controlling caching, accept types or the User-Agent, their values may be overriden by this WebView’s defaults.
Может кто-то из знающих подскажет, в чем проблема или же подскажет, как правильно реализовать загрузку страницы с авторизационными куками?
- Вопрос задан более трёх лет назад
- 6821 просмотр
Проблема решается перекрытием в WebViewClient метода shouldInterceptRequest(). WebView подставляет куки не во все запросы (в частности при обращении к ресурсам типа картинок, js, css, . не подставляет), из-за чего имеем описанную выше проблему.
У конструктора WebResourceResponse первые два параметра mimeType и encoding, которые мы можем получить из заголовка response. Но в моем случае, чёрт знает по какой причине, если передавать их в конструктор — получаю 400 Bad Request.
Может не совсем в тему. Бадался с cookie в своем приложении, использовал Retrofit 2 и OkHttp3 (сервер тоже свой — nginx), сколько ни пробовал примеров с getDefaultSharedPreferences() не получалось сохранить ничего кроме PHPSESSID. Решил вручную записывать через SharedPreferences editor.putString(name, value ); научился сохранять и посылать cookie, но сервер не всегда адекватно на них реагировал: заметил, что если PHPSESSID стоит в конце списка посылаемых cookie, то все нормально, иначе сервер высылает код новой сессии. Когда сложил все cookie в одну строку все заработало.
public class AddCookiesInterceptor implements Interceptor <
public static final String PREF_COOKIES = «PREF_COOKIES»;
// We’re storing our stuff in a database made just for cookies called PREF_COOKIES.
// I reccomend you do this, and don’t change this default value.
private Context context;
public AddCookiesInterceptor(Context context) <
this.context = context;
>
@Override
public Response intercept(Interceptor.Chain chain) throws IOException <
Request.Builder builder = chain.request().newBuilder();
Log.i(«MyCookie»,»————————————«);
G_.cookie = PrefStorage.getAllProperty();
String val=»»;
for(Map.Entryentry : G_.cookie.entrySet()) <
val += (String)entry.getValue()+»; «;
>
builder.addHeader(«Cookie», val);
Log.i(«MyCookie»,val);
Log.i(«MyCookie»,»————————————«);
public class ReceivedCookiesInterceptor implements Interceptor <
private Context context;
public ReceivedCookiesInterceptor(Context context) <
this.context = context;
> // AddCookiesInterceptor()
@Override
public Response intercept(Chain chain) throws IOException <
Response originalResponse = chain.proceed(chain.request());
if (!originalResponse.headers(«Set-Cookie»).isEmpty()) <
String tmp;
for(String header : originalResponse.headers(«Set-Cookie»)) <
tmp = header.split(«=»)[0];
PrefStorage.addProperty(tmp, header);
>
>
public class PrefStorage < // обязательно инициализировать
public static final String STORAGE_NAME = «StorageName»;
private static SharedPreferences settings = null;
private static SharedPreferences.Editor editor = null;
private static Context context = null;
public static void init( Context cntxt ) <
context = cntxt;
>
Источник
Cookie Manager Class
Definition
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Manages the cookies used by an application’s WebView instances.
Remarks
Portions of this page are modifications based on work created and shared by the Android Open Source Project and used according to terms described in the Creative Commons 2.5 Attribution License.
Constructors
A constructor used when creating managed representations of JNI objects; called by the runtime.
Properties
Returns the runtime class of this Object .
(Inherited from Object)
The handle to the underlying Android instance.
(Inherited from Object)
Gets whether there are stored cookies.
Gets the singleton CookieManager instance.
This API supports the Mono for Android infrastructure and is not intended to be used directly from your code.
This API supports the Mono for Android infrastructure and is not intended to be used directly from your code.
Methods
Gets whether the application’s WebView instances send and accept cookies.
Gets whether the WebView should allow third party cookies to be set.
Gets whether the application’s WebView instances send and accept cookies for file scheme URLs.
Creates and returns a copy of this object.
(Inherited from Object)
Indicates whether some other object is «equal to» this one.
(Inherited from Object)
Ensures all cookies currently accessible through the getCookie API are written to persistent storage.
Gets cookie(s) for a given uri so that it can be set to «cookie:» in http request header.
Returns a hash code value for the object.
(Inherited from Object)
Called by the garbage collector on an object when garbage collection determines that there are no more references to the object.
(Inherited from Object)
Wakes up a single thread that is waiting on this object’s monitor.
(Inherited from Object)
Wakes up all threads that are waiting on this object’s monitor.
(Inherited from Object)
Removes all cookies.
Removes all cookies.
Removes all expired cookies.
Removes all session cookies, which are cookies without an expiration date.
Removes all session cookies, which are cookies without an expiration date.
Sets whether the application’s WebView instances should send and accept cookies.
Sets whether the application’s WebView instances should send and accept cookies for file scheme URLs.
Sets whether the WebView should allow third party cookies to be set.
Sets a single cookie (key-value pair) for the given URL.
Sets a single cookie (key-value pair) for the given URL.
Sets the Handle property.
(Inherited from Object)
Returns a string representation of the object.
(Inherited from Object)
Causes the current thread to wait until another thread invokes the java.lang.Object#notify() method or the java.lang.Object#notifyAll() method for this object.
(Inherited from Object)
Causes the current thread to wait until another thread invokes the java.lang.Object#notify() method or the java.lang.Object#notifyAll() method for this object.
(Inherited from Object)
Causes the current thread to wait until another thread invokes the java.lang.Object#notify() method or the java.lang.Object#notifyAll() method for this object.
(Inherited from Object)
Explicit Interface Implementations
| IJavaPeerable.Disposed() | (Inherited from Object) |
| IJavaPeerable.DisposeUnlessReferenced() | (Inherited from Object) |
| IJavaPeerable.Finalized() | (Inherited from Object) |
| IJavaPeerable.JniManagedPeerState | (Inherited from Object) |
| IJavaPeerable.SetJniIdentityHashCode(Int32) | (Inherited from Object) |
| IJavaPeerable.SetJniManagedPeerState(JniManagedPeerStates) | (Inherited from Object) |
| IJavaPeerable.SetPeerReference(JniObjectReference) | (Inherited from Object) |
Extension Methods
Performs an Android runtime-checked type conversion.
Источник
Как установить cookie в клиенте Android WebView
Я хочу вызвать один конкретный URL-адрес через WebView . Страница может быть вызвана только после того, как пользователь уже вошел в систему. Я использую библиотеку AsyncHttpClient для выполнения вызова входа. После успешного входа в систему загрузка URL-адреса через WebView , похоже, не распознает правильные заголовки, например cookie. Я подозреваю, что файлы cookie неправильно синхронизируются между HttpClient и WebView’s HttpClient . Есть идеи, почему? . Вот как я использую WebView
Ценю твою помощь .
3 ответа
Ох, через несколько часов, я наконец понял, что это сработало. Во-первых, CookieSyncManager устарел в более поздних версиях Android. поскольку api 21 согласно док. Поэтому решил больше не использовать. Во-вторых, CookieManager используется для хранения файлов cookie для WebView .
Финальный код
Ключевые изменения в решении: использовать cookie.getDomain () вместо явного домена.
Попробуйте этот код, после нескольких изменений у меня работает:
Моя проблема была немного другой, но ответ от @Tixeon дал мне ключ к ее решению. Я составлял свой файл cookie и добавлял его в запрос WebView, но обнаружил, что Android переопределяет мой файл cookie и отправляет свой собственный файл cookie. Итак, прежде всего мне пришлось удалить все файлы cookie из массива, а затем создать свой собственный файл cookie. Это пример кода:
Теперь запрос содержит мой файл cookie, а не тот, который по умолчанию предоставляется Android, и мой сеанс в WebView работает. Надеюсь, это поможет кому-то другому
Источник
Android studio cookie manager
This Cookie Manager allows you to quickly view and edit specific cookies. It is designed to be compatible with Chrome, Firefox and Firefox for Android.
By default, the Cookie Manager opens when the extension starts up. This allows you to keep the extension disabled until you need it.
You can also turn off the automatic opening, and manually open the cookie manager by clicking on the extension button in the toolbar (desktop) or the Cookie Manager menu item (Firefox for Android 55+).
Cookie Manager is created by Rob Wu rob@robwu.nl (https://robwu.nl/). If you have suggestions or questions, open an issue at https://github.com/Rob—W/cookie-manager/issues or send me a mail.
- Viewing all cookies
- Querying cookies by any combination of url, domain, path, cookie content (name/value), httpOnly/secure/sameSite/session flags, expiration time range.
- Recognizes cookie jars (default, private browsing mode, container tabs aka userContext).
- Allows you to remove individual cookies, or all matching cookies with one click.
- Supports Firefox for Android (Fennec)
- Supports the TOR Browser (and first-party domain cookies)
- Add cookies
- Edit cookies
- Import / export cookies
- JSON format for backup and restoration purposes.
- Netscape HTTP Cookie File format for use with other tools like curl and wget.
Searching for cookies
The Cookie Manager has a search form that allows you to filter on every possible cookie field or flag. Only non-empty filters are used in the query. Wildcards ( * ) can be used in each filter to match any text.
The list of results is not automatically updated. The «Search» button needs to be clicked again to refresh the list of cookies.
Currently the UI is optimized for use on mobile, and support for keyboard shortcuts is limited to the rows in the result table:
- Arrow up Focus the previous cookie row.
- Shift + Arrow up Focus the previous cookie row and extend the current selection (or lack thereof) to that row. This shortcut is ignored when text has been selected.
- Page up and Home are also supported.
- Arrow down Focus the next cookie row.
- Shift + Arrow down Focus the next cookie row and extend the current selection (or lack thereof) to that row. This shortcut is ignored when text has been selected.
- Page down and End are also supported.
- Spacebar Toggle selection of the focused row.
- Delete Remove the focused cookie.
Bulk cookie selection
The Cookie Manager is optimized for the use case of selecting many cookies and then removing them. Being able to quickly select specific cookies is important, so there are multiple ways to select cookies.
Individual cookies can be added or removed from the selection by clicking on a cookie row. All results can be selected by one click on the «Select all» button.
Bulk selection by mouse
When you select text in the results with a mouse, and the text selection contains two or more cookies, then two buttons appear near the mouse pointer:
- «Select n rows» — adds the cookie rows to the cookie selection.
- «Invert selection» — toggles the cookie selection of the cookie rows.
Bulk selection by keyboard
Click on a cookie and use arrow up/down to go to the previous/next cookie row. Press spacebar to toggle the selection.
You can also hold Shift pressed and then press the arrow up/down key to quickly select consecutive rows (or unselect, if the initial row was unselected).
Bulk selection of visible cookies
The default «Select all» button selects all cookies in the search results. To only select the cookies that are visible on the screen, go to the «More actions» menu and change the «Bulk selection» option from
«Select all = select all results» to
«Select all = select visible results».
After doing this, the «Select all» button is replaced with «Select visible».
Because mobile devices do usually not have a physical keyboard or mouse, this button is usually the fastest way to process a large number of cookies.
No special notes. I haven’t published the extension to the Chrome Web Store.
Firefox for Desktop
No known bugs or limitations.
Version 58 and earlier
The cookies API in Firefox has several bugs that makes it unsuitable for modifying (private) cookies. In these cases, after a prompt, the extension will work around the bugs by initiating a request to the sites of the cookies, and modify the cookies when the server sends any response (and abort the request as soon as possible). If the server is unreachable, the cookie cannot be modified.
As of Firefox 56, no work-arounds are needed when the browser runs with the default settings.
When First Party Isolation is enabled (this is the case in the TOR Browser), the work-around is needed, until https://bugzil.la/1381197 is fixed.
And until https://bugzil.la/1381197 is fixed, a «NID» cookie for the google.com is hidden from the cookie manager. This is because the cookie is in a cookie jar used for Safebrowsing, and this jar is completely isolated from the rest of the browser, including extensions (https://bugzil.la/1362834).
Version 55 and earlier
To edit private browsing cookies, the cookie manager must be opened in a private browsing window. If you try to edit a private browsing cookie of a site on the Tracking protection blocklist, then you must temporarily disable Tracking protection, via the «Tracking protection» checkbox at Settings > Privacy (or open a new tab in a private browsing window and flip the «Tracking Protection» switch at the bottom).
Firefox for Android
Version 56 and later
There are no known bugs for the default use case.
Version 55 and earlier
To edit private browsing cookies, the cookie manager must be opened in a private browsing tab (select the URL in the location bar, open an incognito tab, paste the URL and go). If you try to edit a private browsing cookie of a site on the Tracking protection blocklist, then you must temporarily disable Tracking protection, via the «Tracking protection» checkbox at Settings > Privacy.
Version 54 and earlier
There Cookie Manager cannot be opened via the menu (https://bugzil.la/1331742).
Version 53 and earlier
The Cookie manager cannot be opened upon start-up. Tap on the icon in the address bar to open the cookie manager. Due to a bug in Firefox this icon is very small, unfortunately.
About
Cookie Manager for Firefox (Desktop/Android), Chrome. Supports viewing and editing of cookies and private cookies.
Источник
