Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PHPSESSID contains whitespace #2369

Closed
tarumes opened this issue Sep 21, 2022 · 4 comments · Fixed by #2370
Closed

PHPSESSID contains whitespace #2369

tarumes opened this issue Sep 21, 2022 · 4 comments · Fixed by #2370

Comments

@tarumes
Copy link

tarumes commented Sep 21, 2022

Versions

Pi-hole version is v5.12.2 (Latest: v5.12.2)
AdminLTE version is v5.15.1 (Latest: v5.15.1)
FTL version is v5.18.1 (Latest: v5.18.1)

Platform

PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"

Expected behavior

PHPSESSID does not contain aditional whitespaces

Actual behavior / bug

PHPSESSID contains whitespace

Steps to reproduce

get PHPSESSID via code

res, err := http.Get("http://pi.hole")
if err != nil {
	log.Fatal()
}
for _, v2 := range res.Cookies() {
	if v2.Name == "PHPSESSID" {
		fmt.Printf("Site:%s\n%s '%s'\n", v, v2.Name, v2.Value)
	}
}

Screenshot 2022-09-21 152853

@yubiuser
Copy link
Member

Thanks for your report. Did you check you can reliably reproduce it? I just looked at my PHPSESSID and it does not contain spaces

@yubiuser
Copy link
Member

Ok, I see it now. The cookie is correct, but the sent header contains the whitespace.

@yubiuser yubiuser linked a pull request Sep 21, 2022 that will close this issue
1 task
@yubiuser
Copy link
Member

#2370 Should fix the issue.

You can try it yourself with pihole checkout web no_space. To go back on track and before the next update run pihole checkout web master

@tarumes
Copy link
Author

tarumes commented Sep 21, 2022

thx yes your PR fix it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants