Skip to content
This repository has been archived by the owner on Dec 14, 2018. It is now read-only.

Consider making Anti Forgery internal classes public. #1137

Closed
harshgMSFT opened this issue Sep 15, 2014 · 2 comments
Closed

Consider making Anti Forgery internal classes public. #1137

harshgMSFT opened this issue Sep 15, 2014 · 2 comments
Assignees
@rynowak
Labels
3 - Done enhancement
Milestone
1.0.0-beta6

Comments

@harshgMSFT
Copy link
Contributor

Most of the Anti forgery classes are internal today, the main reason for that is we do not want to expose the internal details as we have never come across users wanting to replace the AF sub system.
However this does not seem to be a functional limitation and hence we want to review and see if the classes can be made public.
@harshgMSFT harshgMSFT mentioned this issue Sep 15, 2014
Merged
@danroth27 danroth27 added this to the 6.0.0-rc1 milestone Sep 16, 2014
@yishaigalatzer yishaigalatzer modified the milestones: 6.0.0-rc1, 6.0.0-beta3 Jan 11, 2015
@yishaigalatzer yishaigalatzer modified the milestones: 6.0.0, 6.0.0-rc1 Feb 2, 2015
@yishaigalatzer yishaigalatzer changed the title Consider making AF internal classes public. Consider making Anti Forgery internal classes public. Feb 2, 2015
@danroth27 danroth27 modified the milestones: 6.0.0-beta6, 6.0.0-beta5 May 6, 2015
@rynowak
Copy link
Member

rynowak commented Jun 23, 2015

Fixed here: aspnet/Antiforgery@9eeb1de

will close this issue once MVC is updated to make use of the new Antiforgery codebase.

@rynowak
Copy link
Member

rynowak commented Jun 25, 2015

Done in Beta6. See here: aspnet/Announcements#34

@rynowak rynowak closed this as completed Jun 25, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@rynowak rynowak

Labels
3 - Done enhancement
Projects
None yet
Milestone
1.0.0-beta6
Development

No branches or pull requests
4 participants
@yishaigalatzer @rynowak @danroth27 @harshgMSFT