400 Bad Request Error [Tracking]

#8

Iā€™ve reported the few cases Iā€™ve known about and theyā€™ve replied disabling do not track solves for now, the more people who have this error if they could post up itā€™d be great to relay this to developers

#9

Thanks @Infinity. Based on my simple form, I assume this must impact everyone with an html form on their site, which surely is most people? Telling us to tell all our site visitors to change their browser settings is mad!

That said, Iā€™ve just tried enabling the ā€˜Send a ā€œDo Not Trackā€ request with your browsing trafficā€™ in my Chromiumā€¦ even clearing the cache afterwards, it didnā€™t fix the issue for me.

As @Infinity says, please can others post to confirm if they have this issue too? It will really help get some focus on this

#10

Well add me to the list, however it has only been reported to me on Chrome for Android. All on Oreo. My login page loads fine, but landing page after login receives the Bad Request.

^This!.. Mad, and simply not possible or professional.

Look forward to a solution from you guys ASAP, as this is isolated only to 000webhost from what I have been able to find.

Edit: Checked with one user. ā€œDonā€™t Trackā€ does NOT solve the problem, even when clearing cache and cookiesā€¦

#11

The ticket is still open with developers please all affected post your site URL and describe when the scenario happens like when submitting a post request or logging into a script etc

#12

@Infinity, talentscout.cf/NRL/login is the dodgy page on my site, and some Chrome users have problems when POSTing with a submit button from the modal login form.

Thanks for the follow up.

#13

Thanks Iā€™ve added it to the ticket for a developer to check on.

#14

Is there still no update on this @Infinity?

Iā€™ve had more users reporting this problem to me in the last few daysā€¦

#15

I added a site to the list on the 23rd and 4 hours ago developer replied saying they are still busy with it and other things

#16

Thanks again for the reply @Infinity, Iā€™ve been trying to get to the bottom of it again myself but without knowing too much about the 000webhost server setup its hardā€¦

As far as I can tell, the default number of allowable header fields should far exceed what Iā€™m usingā€¦ I started with 19 this morning, and now Iā€™ve edited my site to get it down to 12, and yet Iā€™m still getting the same error message of exceeding the numberā€¦ This was by combining my include resources and also disabling some features of CloudFlare that required a request header.

Perhaps the error wording is misleading, and weā€™re looking in the wrong place as I highly doubt 12 request headers are exceeding any limitā€¦

EDIT: Confirmed, also only 12 request headers when direct to mysite.000webhostapp.comā€¦ and yet fully accessible by the affected browser.

#17

@Infinity, can you please specify the number of request header fields allowable on the free plan? Also, any length limits imposed on your servers.

NOTE: Disregard my debugging notes in my previous post, as I had misreadā€¦ I was minimizing request headers, not the number of fields contained within one headerā€¦

I feel that I am making progress on getting to the bottom of this issue, and I am now leaning to the cause being the limitation you guys (000webhost) have put on your free plans discussed here:

The relevant Apache setting here is the LimitRequestFields Directive defined as:

Description: Limits the number of HTTP request header fields that will be accepted from the client
Syntax: LimitRequestFields number
Default: LimitRequestFields 100
Context: server config, virtual host
Status: Core
Module: core

The default Maximum number of fields has obviously been significantly reduced from 100 for the free plans as alluded to in the linked post, resulting in my ~15 fields teetering on the edge of allowable. If this can be confirmed by admin or a dev Iā€™m willing to move on, and mark this as closed.

Thanks again for looking into this.

#18

28 Feb 07:06am GMT

Developer replied:

Finally got some good news! This got already fixed on our end, and clients will stop having any issues either today or tomorrow :slight_smile:

So give it a day maybe?
Iā€™ve linked your latest reply to them just in case.

Pass on current limits currently but I can ask.

#19

Strugling to get that right with my website edurga.000webhostapp.com which does not succeed login when accessed diredtly and when visited through Cloudflare gives Bad Request 400 error

#20

Thanks for the update @Infinity!

I have spoken to 3 users that had the error previously, and 2 of them have had the issue resolved which is great news. It would be good to iron out the problem fully, so can you confirm it was the LimitRequestFields directive on your servers causing the issues? Can you please tell me what this has been set to now for the Free plan?

Thanks again.

#21

Iā€™ve not had any response regarding the fields length etc but I had to add another website to the list and he is going to get back to me after the team working on this gets back to him.

#22

Added your site and another userā€™s site to the list.
Apologies.

#23

Developer replied.
"
Yes, LimitRequestFields have been causing the issues previously. It was set to 30 before, and now this limit has been removed completely"

#24

well, my website still having the same problem 400 Error whenever I try to submit games throw form to the website it returns 400 Error on chrome but work fine on firefox.
ovongames.tk

#25

Request error hasnā€™t be resolved completely yet, developer will let me know when.

#26

Any updates on this yet @Infinity?

#27

6th March: Yes, LimitRequestFields have been causing the issues previously. It was set to 30 before, and now this limit has been removed completely :slight_smile:

11th March: Okay, so Iā€™ve just tested this out with my own website, and it works with Do Not Track turned on.
The first time users might get a ā€œYour browser doesnā€™t support cookiesā€ error, but it should work perfectly fine after submitting the form a second time. I believe this is caused by wordpress now.
But overall - should be just fine.
Let me know if there are any further issues with this.