cgicc-help
[
Top
][
All Lists
]
Advanced
[Date Prev][
Date Next
][Thread Prev][
Thread Next
][
Date Index
][
Thread Index
]
[Cgicc-help] Why is not "\r\n\r\n" but "\n\n" for end of http header?
From
:
易剑
Subject
:
[Cgicc-help] Why is not "\r\n\r\n" but "\n\n" for end of http header?
Date
:
Thu, 22 Dec 2016 16:13:58 +0800
Why is not "\r\n\r\n" but "\n\n" for end of http header?
void
cgicc::HTTPContentHeader::render(std::ostream& out)
const
{
out << "Content-Type: " << getData() << std::endl;
std::vector<HTTPCookie>::const_iterator iter;
for(iter = getCookies().begin(); iter != getCookies().end(); ++iter)
out << *iter << std::endl; // "\r\n"
out << std::endl; // "\r\n"
}
reply via email to
[Prev in Thread]
Current Thread
[Next in Thread]
[Cgicc-help] Why is not "\r\n\r\n" but "\n\n" for end of http header?
,
易剑
<=
Next by Date:
[Cgicc-help] Why cgicc not use "\r\n" for http header but std::endl?
Next by thread:
[Cgicc-help] Why cgicc not use "\r\n" for http header but std::endl?
Index(es):
Date
Thread