Hi Batuhan,

You can try http://christopherthielen.github.io/ui-router-extras/#/future 
for lazy states loading.
I personally differentiate the admin and the user functionality into 
separate apps, and I'm always trying do not include any sensitive data into 
client-code.

Best regards, Pavel

Hi,
>
> Sorry if the question is too basic (or too dumb) but I am new to Angular 
> and, in general, client-side JS frameworks that move app logic to the 
> client. I am more of a .NET guy exploring out of his little shell :)
>
> I have done a simple single page app with a .net backend and when I 
> inspect the page in Chrome, naturally, I can see all of the scripts, 
> backend service address, port numbers, parameters, etc... Also if you have 
> hidden pages like admin pages which require login, their URLs are clearly 
> seen in the router config lines which may cause hacking attempts. Of course 
> I will secure these pages with tokens etc... but making these urls visible 
> to an unauthenticated user just feels unsafe.
>
> I am clear that I do not know much about Angular yet, so this is probably 
> my lack of knowledge. But is there a way to keep this sensitive information 
> secure somehow? For example, if the user is not logged in he gets a 
> different router config but if he logs in, he gets the admin pages added to 
> the router config. Or another example, running ng-hide or ng-show 
> directives on the server side with the client getting only the final 
> result, not the actual content fragment that I am trying to hide?
>
> In short I suppose I am trying to ask if there is some "code-behind" 
> concept in Angular.
>
> Thank you for your help.
>

-- 
You received this message because you are subscribed to the Google Groups 
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.

Reply via email to