it turns out that the issue is the server needing to check the JSESSIONID found in the cookie. So what I need to end up doing is to send a "fabricated" cookie along with my requests. No I am not trying to hack anything, but merely allow myself to test the code using an external mock client web app.
Any guidance or sample code on how to hand craft a cookie and how to send that along with the http requests? Regards, Reza On Wed, Apr 19, 2017 at 7:42 PM, Sander Elias <[email protected]> wrote: > Hi Reza, > > It looks like you are trying to load a page that's designed to be loaded > in a browser/iframe directly. I highly doubt it has anything to do with > angular. Look in the dev-tool network tab at what you are receiving. > > Regards > Sander > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Angular and AngularJS discussion" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/angular/mTTtrIdntXg/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/angular. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" 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 https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
