[ 
https://issues.apache.org/jira/browse/CB-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959597#comment-13959597
 ] 

ASF GitHub Bot commented on CB-6389:
------------------------------------

Github user mbradshawabs commented on the pull request:

    
https://github.com/apache/cordova-plugin-inappbrowser/pull/34#issuecomment-39528726
  
    The answer for #1 is no, unfortunately, which is the reason why I want this 
functionality and why I am clearing cookies.  If you close() inappbrowser and 
open the same url, you get your cookies and your session back intact.  
    
    The docs for clearsessioncache (on 
https://cordova.apache.org/docs/en/3.0.0/cordova_inappbrowser_inappbrowser.md.html)
 indicate that it clears the session cookie cache on android.  So it seems that 
what we've got now is actually in parity with android.  Though I completely 
agree that the name of the property is a bit misleading.  'clearcookies' does 
make tons more sense as a name, but I *think* that we are probably better off 
just duplicating the android functionality even with a bad name.
    
    In any case, what I really need is to be able to clear cookies, not the 
cache, so whatever the name ends up being I want to maintain the functionality.


> Add clearsessioncache option for iOS
> ------------------------------------
>
>                 Key: CB-6389
>                 URL: https://issues.apache.org/jira/browse/CB-6389
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: iOS, Plugin InAppBrowser
>    Affects Versions: 3.4.0
>         Environment: iOS
>            Reporter: Mark Bradshaw
>            Priority: Minor
>              Labels: features
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Android has a clearsessioncache option that is missing in the iOS version.  
> This, being a useful feature, is something I'd like to add.  The changes are 
> fairly minor, and I will issue a pull request with the needed code changes.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to