All right, so we have learned a lot of detail about the network interception from our last section
through this section, and we know how we can intercept the networks and stuff.
I mean, we can do even a lot more things in this network interception beyond what we can see here.
And once again, as I told you, our imagination is only the limit of extending this particular network
interception.
We can do almost anything with this network interception much easily.
This is one of the feature which is completely missing from selenium.
I mean, certainly AMPHORA does have the network interception capability like CDPR sessions, but that
is very, very tough to do.
I mean, the code that you write is very, very, super hard coded and you cannot really write a code
which is pretty nice and better than this kind of code.
So I definitely am sure that this network interception with playwrite is one of the greatest advantage
of making this tool much, much better.
Well, as I said, we are going to talk today in this lecture about the cookies.
I mean, the cookies is the most common thing that we know about any cell site that actually has cookies
and how we can actually work with cookies and stuff.
Cookies is one of the most old technique of storing your information stuff.
Ammonite right now at many sites are not even storing a lot of data on the cookies.
They are using different way of working with like Web workers and different way of caches.
I mean, cookies is not a way to store sensitive information.
So nowadays but there are some cases where you still need to go with cookies in some legacy websites
and some sites still lives cookie heavily.
So if you go to a website, let's take our exit automations year app Dorsami dot com website.
And if you just inspect the site over here and if I just go to the application and if you can see here,
there is a cookie of its peanut S.A.T. that is a request verification, Nidhi, which is something dynamic,
which is lot on the fly.
And there's a request verification token, which is a dynamic token just to see if this request is generated
by a specific browser, specific time, something like that.
This is how I wrote this particular app a long time before.
Once a login that is going to be an application cookie, which is going to ensure that this particular
cookie is being set by this particular application, by this particular user and stuff.
So this is what is this particular cookie?
I mean, if you try to decrypt this cookie, you will see some user information and things of that nature.
And the same origin policy is also, as I said, over here with LAX.
Yep.
And now I need to somehow set a cookie on this particular website and I need to see how I can log in
to this application without actually logging in, just using the cookies, how I can be able to log
within the site and access the employee details and things of that nature.
So you know that if this particular website, if I don't log in, you don't see the create new button,
you can't even click to create your buttons and stuff.
But you can still go to the create new, uh, like that create.
You can go here, but you can't really create it unless until you log in.
So that is super important things.
I mean, you need to have these cookies at least been set.
So in order for that we need to somehow obtain the cookie and then we need to set the cookie on this
particular site and work with it.
This is what we are going to be doing in this particular lab and we'll see how we can actually achieve
this.
We were talking more about that in our next lecture.
But if you could able to achieve this yourself, just give a shot and see how you can do it.
I mean, it's a very, very straightforward thing.
It's not a big deal.
While back in India.
Well, I was doing it like a long time before using J meters.
I could be able to achieve that in J Meter very, very easily.
I think that is something that you can achieve much easily as well.
Just give a shot if you can't really do it yourself, if you're going to talk about it in your next
lecture.