Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Copy isSecure() property from JSR356 Session #2512

Merged

Conversation

slovdahl
Copy link
Contributor

@slovdahl slovdahl commented Aug 9, 2024

Without this, it's impossible to know if a connection is done using SSL or not.

Without this, it's impossible to know if a connection is done using SSL or not.
@slovdahl slovdahl force-pushed the copy-secure-property-from-JSR356-session branch from 5e79d38 to 32b20ab Compare August 9, 2024 10:19
@jfarcand jfarcand merged commit cae548f into Atmosphere:main Aug 9, 2024
3 checks passed
@slovdahl slovdahl deleted the copy-secure-property-from-JSR356-session branch August 10, 2024 18:52
@slovdahl
Copy link
Contributor Author

@jfarcand do you mind if I publish 3.0.9 with this fix?

@slovdahl
Copy link
Contributor Author

Side note, should we switch the default branch to main and also remove this line from the README?

Main development branch is atmosphere-2.7.x Only pull request for that branch will be accepted.

@jfarcand
Copy link
Member

jfarcand commented Aug 10, 2024 via email

@jfarcand
Copy link
Member

jfarcand commented Aug 10, 2024 via email

@slovdahl
Copy link
Contributor Author

slovdahl commented Aug 10, 2024

Hmm, I published 3.0.9 built with JDK 8 😁 It did build without problems. But I now noticed that the README says 3.0.x requires JDK 11. Should I rebuilt it with 11 and publish 3.0.10? 🤔

@slovdahl
Copy link
Contributor Author

I'm redoing the release as 3.0.10 built with JDK 11.

@slovdahl
Copy link
Contributor Author

@jfarcand I don't have access to change the default branch. But I have now updated README.md in the main branch to be up to date, so whenever you have time, please change the default branch for the repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants