Joe Audette

In the api section it mentions requestParams requestParams - Default value []. Parameters which will be passed with each request to the connector. couldn't that be used to pass xsrf...

@servocoder requestParams still exists and works for passing extra params right? so it could be used for this purpose right? I am asking for myself, whether that solution satisfies others...

I agree requests that make changes or do operations should all be post not get. I wish requestParams did work, I think that would be sufficient solution, and more general...

I agree, cookie seems a not great idea for this. If I understand how xsrf attacks work, they take advantage of the fact that a user is logged into some...

There are definitely solutions that do use hidden form fields aka request parameters. Cookies is one solution, but it has some drawbacks, ie it is passed with every request, even...

not to say I'm against the cookie to header idea, as long as we get a solution that works, but I am also not sure the header name used is...

I managed to get my project template to create the folder structure I want and a .sln file ie: |-src >|-WebApp >>|-WebApp.csproj WebApp.sln It works as I wish using dotnet...

sorry but I have lost interest in using this starter myself. only the repo maintainer can accept a pull request so no point in making one if he is not...

ok, done

RTM ships on June 27, so you might as well skip an rc2 version at this point unless it also will support RTM