Cookie fix

[kabugge]

Describe the bug

https://blog.csdn.net/gitblog_00060/article/details/151495613
Please see. Is this fix merged in?

Reproduction Steps

https://blog.csdn.net/gitblog_00060/article/details/151495613

Expected Behavior

Cookie should be OK.

Current Behavior

Seems cooke.v is buggy.

Possible Solution

No response

Additional Information/Context

No response

V version

the newest

Environment details (OS name and version, etc.)

ALL

Note

You can use the 👍 reaction to increase the issue's priority for developers.

Please note that only the 👍 reaction to the issue itself counts as a vote.
Other reactions and those to comments will not be taken into account.

[huly-for-github]

Connected to Huly®: V_0.6-26224

[felipensp]

The cookie.v file mentioned is exactly same on V repository.

[kabugge]

@felipensp Hello, I think the link of the cookie.v file mentioned is not correct. Please see the body of the article, I think his fix is pretty valuable.

[felipensp]

@felipensp Hello, I think the link of the cookie.v file mentioned is not correct. Please see the body of the article, I think his fix is pretty valuable.

Can you provide a PR fixing? Thanks

[kabugge]

Hi @felipensp Please see the below code from the article:

    match state {
        .start {
            if c == ' ' {
                i++
            } else {
                state = .in_name
            }
        }
        .in_name {
            if c == '=' {
                state = .after_name
                i++
            } else {
                current_name += c.str()
                i++
            }
        }
        // 更多状态处理...
        else {}
    }
}

---

"// 更多状态处理..." means more states to handle. And the below else statement("else {}") is empty. So I think the fix may not be intact. And I know nothing about V lang... So I just asked if the fix is merged in. Can you figure out if the code is intact?

[felipensp]

I've used another approach to fix the test case posted on the article.

[kabugge]

Hi @felipensp Thanks for the quick response! The article also mentions a problem in sanitize_cookie_value() function, will you fix it as well?