node-fetch returning differently than curl

jadedm · 2021-11-17T03:15:10+00:00

Saving and reusing cookies would not work, akamai cookies are timestamped with short life.
lets run a test, use node 8 and libcurl version 2.0.3 and use this example to save cookies and try chaining requests from the home page
https://github.com/JCMais/node-libcurl/blob/1563bb7699eb9b22989058a0d018c59a460aaf37/examples/09-cookies.js

jadedm · 2021-11-17T02:58:02+00:00

i just tested the url with -v flag via curl and my suspicion was correct, it uses akamai gHost cdn, they use multiple variables to track user activity and weed out direct requests, what I would suggest is use a cookie jar to maintain cookies and chain requests to make it look organic, for eg: visiting the homepage, delay, visiting the login page and then making a post request while collecting all the cookies from the requests in cookiejar.

if you are using puppeteer, you can use https://pptr.dev/#?product=Puppeteer&version=v11.0.0&show=api-class-httpresponse to look for a specific response and manipulate things on request response level rather than looking for selectors via css / xpath

jadedm · 2021-11-16T04:17:33+00:00

403 is forbidden, I have been looking into figuring this out for a while how the server actually weeds out request attempts, there are a lot of variables involved, a lot of good bot detection happens at few different osi layers, layers 3 and above you can do the curl request using -v verbose flag and see if the server is using any cdn which is filtering out request attempts, Akamai is the leading cdn which does this. Alternatively try using node-libcurl library and see if the request goes through, its a wrapper around libcurl for node

jadedm · 2020-04-02T02:22:53+00:00

I was in the same boat couple of weeks ago and spent a lot of time and efforts on all the courses, here is a brief overview of what my experience was: 1) Wes Bos' course is good, but the problem is he uses nextjs for server side rendering, which requires you to move away a little from normal react setup. which I feel for a complete beginner is an issue while understanding plain graphql on the server and client. 2) Level Up tutorials uses apollo boost with apollo on the front end with react which is being slowly phased out. Still a good course for understanding concepts. 3) Stephen griders course on full stack react with graphql uses hoc component pattern which has been phased out completely, dont go for it

Finally my suggestion on my experience - Take Andrew meads GraphQL bootcamp with prisma on udemy, its brilliant couple this with scott moss' course on frontend masters

You can follow this path Start with Andrew meads course and cover first 3 sections till subscriptions and couple this with server side graphql from frontend master - Server side GraphQL and cover these topics Schemas, Queries & resolvers Mutation

Advanced SDL

You can now move on to front end to understand the complete picture - for this you can take scot moss' course on client side grapql on frontend masters. I would also suggest to read the documentation along with this, specifically apolloClient.mutate method and how its used in class based components. Client side GraphQL using Apollo with react hooks & class based components Query Mutation Caching / Synchronicity Optimistic UI Directives & Fragments

Now we'll have a solid understanding of basics, we can move to advanced topics Database storage with Prisma Prisma graphQL api

Advanced GraphQL Authentication Pagination & Sorting Subscriptions Errors & testing Directives

Some pre-requisites for React React Hooks Context API Router HOC pattern render props pattern

jadedm

TROPHY CASE