Error Buddy
Do you have an error message from your application? Then find the answer with Error Buddy. You can search over 40000 source code files and troubleshooting documents using our beta lucene/nutch search interface or if you prefer, search as normal using google. With LXR technology you can drill right down into the line of source code where it came from with full cross-referencing.
If after searching you didn't get your ideal answer, or you are still unclear what the error means, you can choose to post that question to the community forums following the link included in the search results.
[1.6]001 TODO: 002 ==== 003 004 * Thread safety (started) 005 006 * Documentation (API, tutorial) 007 008 * Use gconf for config data (especially proxy info) 009 010 * Bring back WSDL compiler from old soup module? 011 012 * Bring back SOCKS support? 013 014 * Bring back CGI server support? (Split SoupServer into SoupServerTCP 015 and SoupServerCGI) 016 017 * Handle gzip Content-Encoding 018 019 * Add a SoupMessageFilter implementation to handle cookies (RFC 2965) 020 021 * Add a SoupMessageFilter implementation to handle caching (rcd has 022 some of the logic for this already). 023 024 * More regression tests 025 026 * Add apache config files to tests/ so that apache can be run locally 027 to run regression tests against 028 029 * User-Agent handling: caller should specify a User-Agent string to 030 SoupSession, and soup should automatically append libsoup/#.## to 031 that. (Likewise for Server/Via headers.) 032 033 * Range support 034 035 * NTLM Proxy-Authentication support, GSS-Negotiate support 036 037 * Pipelining 038 039 * Merge SoupAuth and SoupServerAuth 040 041 * Merge SoupMessage and SoupServerMessage (allow chunked requests) 042 043 * Improve SoupServer handlers to allow for expect-continue handling, 044 reading chunked requests a chunk at a time, etc. (Use 045 SoupMessageFilter for consistency.) 046 047 * SoupProxy (based on simple-proxy, but better), which connects a 048 SoupServer to a SoupSession with SoupMessageFilters in between. 049 050 * Add date-parsing/generating routines (all formats) 051 052 * Special handling on server side for HEAD (ignore 053 response->body.length). 054 055 * Warning header support 056 057 058 Known bugs/limitations: 059 ======================= 060 061 * Digest auth does not support qop="auth-int" (both client and server) 062 063 * Trailers in chunked responses are not handled 064 065 * simple-proxy is not very RFC compliant 066 067 * Can't send or receive "OPTIONS * HTTP/1.1" (SoupURL won't accept 068 "*".) 069 070 * Can't implement CONNECT on the server side (no way to steal the 071 socket from the SoupServer). 072 073 074 Conformance: 075 ============ 076 * Check handling of unknown HTTP versions [RFC ????] 077 078 * Don't do HTTP/1.1-specific behavior on HTTP/1.0 messages 079 080 * Preserve header ordering (on send and receive). Treat 081 "Foo:bar\r\nFoo:baz" the same as "Foo: bar, baz" 082 083 * Enforce rules about what requests/responses MUST/MUST NOT have a 084 body 085 086 * Encode space as "+" in URIs. 087 088 * Don't automatically process redirects on non-GET/HEAD requests 089 090 * Properly mangle HTTP/1.0 requests containing Connection headers 091 [14.10] 092 093 * Automatically add Date header in SoupServer 094 095 * MUST observe DNS TTL information 096 097 [get SHOULDs and SHOULD NOTs in]
Testing
