IssueTracker

доколе?

+1
There should be possible to open source in any installed (or minSdk for project) android API version, because compileSdk is not only one used for run the app.

Why it takes so long to release source code to SDK when the sources was already pushed to GIT?

Fuck this issue, always happened from android 23. Fuck this. Not friendly to developers

as a workaround you can attach outdated sources, but hope this will be fixed
https://www.reddit.com/r/androiddev/comments/6ihzli/targeting_api_26_what_do_to_about_those_missing/

yep, no 26 sources no funny ;(
all the bunnies gonna cry ;((

by the way, some temporary workaround https://gist.github.com/J-Swift/539aaf82ffac21d5515274a24379667f but we need the official stuff for sure

+1

[Comment deleted]

SNI is definitely a must. Using named virtual hosts is becoming more and more common and popular (who the hell wants to pay for more IP addresses just because you need another site secured?). Please fix this - make it a priority.

Hi! I have noticed that the status of this has changed to 'released'. In what ersion has is been released? Will it be included in my new Android handset's update (currently on 2.3.3, waiting eagerly for 2.3.4).

atur...@googlemail.com, it is marked Target-Honeycomb, so 3.0.

SNI might work on 2.3 with alternative browsers that have their own https stack, such as Firefox. Usually I test with https://gmail.com

(changing owner since the old username was no longer valid)

Very disappointing that this still hasn't been implemented. Using 2.3.5 on a Galaxy S2, doesn't work in included browser nor in dolphin browser. :/

SNI is also not working in Android 2.3.3 on Droid 2. Perhaps the status or the Target should be updated.

chrishie...@gmail.com, the status is that the issue has been addressed in Honeycomb. There are no plans to address it in earlier releases.

chrishie...@gmail.com :

Non "corporate gibberish" summary :
 * Gingerbread (2.3) Will never get this update officially.
 * Honeycomb (3.0) contains the fix but isn't available on phones.
 * Ice Cream Sandwich (4.0) will provide this feature to phones but isn't already available (soon).

Also :
 * The fix from Honeycomb could have been backported by the manufacturers that got it's source code but none that I know off did it.
 * As Honeycomb is a closed source release none of the alternative distribution could merge the patch without re-developing it.
 * As Ice Cream Sandwitch will include this patch it will be in all distributions and could even be backported to Gingerbread.

Sadly coupled with the fact that google don't control at all the updates of previous phones it lock SNI in an "Unusable for most of Android users" state for 2+ Years at least for environements where you don't control users hardware.

At least now for companies you could plan an upgrade (software or hardware depending on the phone models your employees got) as soon as ICS is released.

If servers choke on TLS extensions, just get the user an error message stating that it's the servers fault, and also remove the fallback from chrome. At some time, server owners will be forced to support state of the art technology like they should.

[Comment deleted]

Hello All,
         I am developer and I am facing the same issue. Do you know how we can overcome this issue from server side.  

sven.k.heinemann, see http://www.imperialviolet.org/2012/04/11/falsestart.html for a discussion of trying to force server owners to upgrade to support state of the art technology like they should.

dipu, the lack of SNI means https sites can be virtual hosted on the same IP. the workaround is to use different IPs for different https hosts. Note this can still be done on one server, it just needs multiple IP addresses to distinguish which request is for which server.