# Why?

**URL:** <https://forum.infinityfree.com/t/why/87336>\
**Category:** Informal\
**Created:** [December 9, 2023, 7:08pm UTC](https://forum.infinityfree.com/t/why/87336 "2023-12-09T19:08:32Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Herbert](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/herbert/32/43603_2.png) [@Herbert](https://forum.infinityfree.com/u/Herbert)\
**Post date:** [December 11, 2023, 3:06pm UTC](https://forum.infinityfree.com/t/why/87336/21 "2023-12-11T15:06:53Z")

</div>

It’s not the client cookie, It’s the website’s cookie.

---

<div class="post-metadata">

**Author:** ![Herbert](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/herbert/32/43603_2.png) [@Herbert](https://forum.infinityfree.com/u/Herbert)\
**Post date:** [December 11, 2023, 3:10pm UTC](https://forum.infinityfree.com/t/why/87336/22 "2023-12-11T15:10:39Z")

</div>

Just to be clear guys, What I showed was a different method. Like @ChrisPAR you can’t directly access using just CURL. So don’t get me wrong for posting things like this.

> [@Herbert](#):
>
> Mmm, I am not sure about apps, but if you want to make a CURL request, you can add headers to it, so it’ll act as a browser. This is how I sent the request to my site. Although CURL doesn’t support JS, in that case you need to add the website’s cookie to the header, or you can set the `--cookie` flag to the request. (If you are using this request on a https request, then you need to modify a bit since CURL is not responding well to https requests.)

---

<div class="post-metadata">

**Author:** ![anon50163844](https://forum.infinityfree.com/letter_avatar/anon50163844/32/6_449c533f586939b6e5f246632a46421f.png) [@anon50163844](https://forum.infinityfree.com/u/anon50163844)\
**Post date:** [December 11, 2023, 11:39pm UTC](https://forum.infinityfree.com/t/why/87336/23 "2023-12-11T23:39:11Z")

</div>

![Screenshot_20231212-063617~2](https://forum-cdn.infinityfree.net/original/3X/5/d/5d464d46effa309d784e0a43ed01f4634e17c545.png)  
\*Big brain emoji  
I guess curl actually works. So there’s no cookie validation whatsoever? But I hit the security system instead 😮

---

<div class="post-metadata">

**Author:** ![YT\_Xaos](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/yt_xaos/32/45201_2.png) [@YT\_Xaos](https://forum.infinityfree.com/u/YT_Xaos)\
**Post date:** [December 12, 2023, 12:12am UTC](https://forum.infinityfree.com/t/why/87336/24 "2023-12-12T00:12:14Z")

</div>

> [@anon50163844](#):
>
> I guess curl actually works.

It does not because:

> [@anon50163844](#):
>
> I hit the security system instead 😮

However, when Herbert did it, it worked, not sure how (and yes I did try to set the cookie).

---

<div class="post-metadata">

**Author:** ![Greenreader9](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/greenreader9/32/22847_2.png) [@Greenreader9](https://forum.infinityfree.com/u/Greenreader9)\
**Post date:** [December 12, 2023, 1:00am UTC](https://forum.infinityfree.com/t/why/87336/25 "2023-12-12T01:00:21Z")

</div>

> [@YT\_Xaos](#):
>
> it worked, not sure how

Because he had the cookie there

---

<div class="post-metadata">

**Author:** ![YT\_Xaos](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/yt_xaos/32/45201_2.png) [@YT\_Xaos](https://forum.infinityfree.com/u/YT_Xaos)\
**Post date:** [December 12, 2023, 1:58am UTC](https://forum.infinityfree.com/t/why/87336/26 "2023-12-12T01:58:26Z")

</div>

That is why I said this:

> [@YT\_Xaos](#):
>
> and yes I did try to set the cookie

I’ll try again in a few minutes or tomorrow (it is 8:59 PM currently and I have school tomorrow).  
–EDIT–  
I just tried it and it worked!  
 ![image](https://forum-cdn.infinityfree.net/original/3X/2/2/221aa4687ee23a2d466f0dc201f57a1d30bf837d.png)

 ![image](https://forum-cdn.infinityfree.net/original/3X/5/1/51a7f169dbca92f72ec2a1f33535e4eaa00efede.png)

---

<div class="post-metadata">

**Author:** ![Herbert](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/herbert/32/43603_2.png) [@Herbert](https://forum.infinityfree.com/u/Herbert)\
**Post date:** [December 12, 2023, 10:39am UTC](https://forum.infinityfree.com/t/why/87336/27 "2023-12-12T10:39:38Z")

</div>

> [@Greenreader9](#):
>
> Because he had the cookie there

That’s correct, without the cookies JS won’t work.

---

<div class="post-metadata">

**Author:** ![Herbert](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/herbert/32/43603_2.png) [@Herbert](https://forum.infinityfree.com/u/Herbert)\
**Post date:** [December 12, 2023, 10:40am UTC](https://forum.infinityfree.com/t/why/87336/28 "2023-12-12T10:40:49Z")

</div>

😀 👍

---

<div class="post-metadata">

**Author:** ![anon50163844](https://forum.infinityfree.com/letter_avatar/anon50163844/32/6_449c533f586939b6e5f246632a46421f.png) [@anon50163844](https://forum.infinityfree.com/u/anon50163844)\
**Post date:** [December 12, 2023, 10:47am UTC](https://forum.infinityfree.com/t/why/87336/29 "2023-12-12T10:47:45Z")

</div>

![Screenshot_99](https://forum-cdn.infinityfree.net/original/3X/2/2/22223b46ce869d9a9d67b75b41e95b50c55ffec8.png)  
still doesn’t work for me

---

<div class="post-metadata">

**Author:** ![YT\_Xaos](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/yt_xaos/32/45201_2.png) [@YT\_Xaos](https://forum.infinityfree.com/u/YT_Xaos)\
**Post date:** [December 12, 2023, 12:12pm UTC](https://forum.infinityfree.com/t/why/87336/30 "2023-12-12T12:12:38Z")

</div>

You are using Herbert’s cookie! Go to dev tools \> Application \> Cookies and copy the value for `__test`.

---

<div class="post-metadata">

**Author:** ![wackyblackie](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/wackyblackie/32/43350_2.png) [@wackyblackie](https://forum.infinityfree.com/u/wackyblackie)\
**Post date:** [December 12, 2023, 12:45pm UTC](https://forum.infinityfree.com/t/why/87336/31 "2023-12-12T12:45:17Z")

</div>

A whole new solution would be to use headless chrome or Firefox. Maybe that would work. I’ve never used a headless browser before, though.

---

<div class="post-metadata">

**Author:** ![anon42008019](https://forum.infinityfree.com/letter_avatar/anon42008019/32/6_449c533f586939b6e5f246632a46421f.png) [@anon42008019](https://forum.infinityfree.com/u/anon42008019)\
**Post date:** [December 12, 2023, 12:46pm UTC](https://forum.infinityfree.com/t/why/87336/32 "2023-12-12T12:46:42Z")

</div>

The whole conclusion for me is that this security system sucks.

---

<div class="post-metadata">

**Author:** ![Greenreader9](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/greenreader9/32/22847_2.png) [@Greenreader9](https://forum.infinityfree.com/u/Greenreader9)\
**Post date:** [December 12, 2023, 1:00pm UTC](https://forum.infinityfree.com/t/why/87336/33 "2023-12-12T13:00:56Z")

</div>

Yeah, that works. Or just re-invent the cookie.

---

<div class="post-metadata">

**Author:** ![Admin](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/admin/32/36437_2.png) [@Admin](https://forum.infinityfree.com/u/Admin)\
**Post date:** [December 12, 2023, 2:34pm UTC](https://forum.infinityfree.com/t/why/87336/34 "2023-12-12T14:34:26Z")

</div>

The cookie is not a static value. You can’t just copy it once and reuse it forever. That would make it way too easy to bypass the security system.

> [@anon42008019](#):
>
> The whole conclusion for me is that this security system sucks.

It sounds to me like it’s doing exactly what it’s intended to do.

---

<div class="post-metadata">

**Author:** ![anon42008019](https://forum.infinityfree.com/letter_avatar/anon42008019/32/6_449c533f586939b6e5f246632a46421f.png) [@anon42008019](https://forum.infinityfree.com/u/anon42008019)\
**Post date:** [December 12, 2023, 3:10pm UTC](https://forum.infinityfree.com/t/why/87336/35 "2023-12-12T15:10:13Z")

</div>

> [@Admin](#):
>
> It sounds to me like it’s doing exactly what it’s intended to do.

Intended to prevent bots from accessing but some easy trick bypasses it.

---

<div class="post-metadata">

**Author:** ![anon50163844](https://forum.infinityfree.com/letter_avatar/anon50163844/32/6_449c533f586939b6e5f246632a46421f.png) [@anon50163844](https://forum.infinityfree.com/u/anon50163844)\
**Post date:** [December 12, 2023, 10:16pm UTC](https://forum.infinityfree.com/t/why/87336/36 "2023-12-12T22:16:52Z")

</div>

How to see devtools on android?

---

<div class="post-metadata">

**Author:** ![YT\_Xaos](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/yt_xaos/32/45201_2.png) [@YT\_Xaos](https://forum.infinityfree.com/u/YT_Xaos)\
**Post date:** [December 12, 2023, 10:29pm UTC](https://forum.infinityfree.com/t/why/87336/37 "2023-12-12T22:29:43Z")

</div>

I don’t have an Andriod so I wouldn’t be able to tell you with certainty that this works but here’s an article:

> **[ניפוי באגים מרחוק במכשירי Android  |  DevTools  |  Chrome...](https://developer.chrome.com/docs/devtools/remote-debugging?hl=he)**
>
> ניפוי באגים מרחוק בתוכן בשידור חי במכשיר Android ממחשב עם מערכת הפעלה Windows, Mac או Linux.

Alternatively, this is what Bing AI told me:

> [@](#):
>
> 1. **Open Chrome** on your Android device.
> 2. **Go to the page** you want to debug.
> 3. **Add `view-source:`** at the beginning of the URL (e.g., `view-source:https://www.example.com`) and press **Enter**. This will display the source code of the page.
> 4. **Tap on any line of the source code**. This will bring up a toolbar at the bottom of the screen.
> 5. **Tap on the “Inspect” icon** (it looks like a magnifying glass) on the toolbar.

---

<div class="post-metadata">

**Author:** ![Herbert](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/herbert/32/43603_2.png) [@Herbert](https://forum.infinityfree.com/u/Herbert)\
**Post date:** [December 13, 2023, 5:22am UTC](https://forum.infinityfree.com/t/why/87336/38 "2023-12-13T05:22:21Z")

</div>

> [@Admin](#):
>
> It sounds to me like it’s doing exactly what it’s intended to do.

Hey Admin, The current cookie security mechanism is indeed preventing bots, but wouldn’t it be more efficient if you set the cookie value to reset for each request? This would improve the system. It’s just an idea, though!

---

<div class="post-metadata">

**Author:** ![anon42008019](https://forum.infinityfree.com/letter_avatar/anon42008019/32/6_449c533f586939b6e5f246632a46421f.png) [@anon42008019](https://forum.infinityfree.com/u/anon42008019)\
**Post date:** [December 13, 2023, 5:33am UTC](https://forum.infinityfree.com/t/why/87336/39 "2023-12-13T05:33:37Z")

</div>

It would unnecessarily slow down page load time + break media linked in it, it would still be bypassable by a bot which uses headless browser.

---

<div class="post-metadata">

**Author:** ![Herbert](https://forum.infinityfree.com/user_avatar/forum.infinityfree.com/herbert/32/43603_2.png) [@Herbert](https://forum.infinityfree.com/u/Herbert)\
**Post date:** [December 13, 2023, 5:38am UTC](https://forum.infinityfree.com/t/why/87336/40 "2023-12-13T05:38:19Z")

</div>

Yeah but it’ll add another security layer though. Why not using CAPTCHA? It’s very effective against bots.

[Previous page](https://forum.infinityfree.com/t/why/87336.md?page=1)

[Next page](https://forum.infinityfree.com/t/why/87336.md?page=3)
