9342e0e593
*replace call of PARSE-REQUEST-URI (relict of old URL parser)
...
with call of URL-STRING->HTTP-URL
2005-04-06 22:45:48 +00:00
2dcdd41ed9
*reinsert lost line
...
*replace calls of UNESCAPE-URI (relict of old URL parser) with UNESCAPE
*simplify URI-HAS-PROTOCOL?
2005-04-06 22:43:53 +00:00
512ccfaed3
removal of old URL parser relicts:
...
*replace calls of UNESCAPE-URI with UNESCAPE
*remove imports of uri package where no longer needed
2005-04-06 22:41:10 +00:00
ed53670895
*add comment explaining why we don't need to support "*" and authority
...
Request-URIS
*comment on when unescaping is done
*don't unescape query when building a http-url record
*don't escape query when unparsing a http-url record.
*remove PARSED-URI->HTTP-URL, integrate its code into
URL-STRING->HTTP-URL
*add dummy encoder ESCAPE-NOT-UNRESERVED-CHARS
2005-04-06 22:31:33 +00:00
745a123735
adapt code to remove calls of URI-PATH->URI (relict of old URL parser)
2005-04-06 12:32:17 +00:00
61a63b4d4b
adapt URI-HAS-PROTOCOL? to new URL parser
2005-04-06 11:59:05 +00:00
0de6fe79b4
replace calls of HTTP-URL->STRING (relict of old URL parser)
...
with calls of HTTP-URL->URL-STRING
2005-04-06 11:44:28 +00:00
17a46a7e71
rename URI-STRING->HTTP-URL to URL-STRING->HTTP-URL
2005-04-06 11:35:37 +00:00
5836ae567b
export HTTP-URL-PATH->PATH-STRING in url-interface
2005-04-05 18:45:53 +00:00
9399bf9397
remove MY-REPORTED-PORT (relict of old URL parser)
2005-04-05 18:45:02 +00:00
da10de6309
add function HTTP-URL-PATH->PATH-STRING (unparses path in http-url record into string)
2005-04-05 18:43:23 +00:00
e5c8cae17f
rename HTTP-URL->URI-STRING to HTTP-URL->URL-STRING
2005-04-05 10:59:13 +00:00
1e93a6cb9f
rename PARSE-URI to PARSE-URL
2005-04-05 10:50:12 +00:00
c3b855ae22
minor changes:
...
*HTTP1.1 (this is wishful thinking)
*we don't have a general URI parser, just a URL parser
*typos
*alles irdische hat einen namen
2005-04-04 21:23:16 +00:00
3548b25c26
rename HTTP-URL-SEARCH to HTTP-URL-QUERY (adaption to restructured
...
http-url type in url.scm)
2005-04-04 21:13:35 +00:00
d0c64d371a
further restrict url-interface
2005-04-04 21:10:05 +00:00
46645ccd58
*remove definition of PARSE-REQUEST-URI (relict of Olin's old URL parser)
...
*use URI-STRING->HTTP-URL instead
2005-04-04 21:07:55 +00:00
d864e4da80
correct reference in comment
2005-04-04 20:57:36 +00:00
cf747a97b4
*add solution for mistake in RFC 2616 (where query part of
...
Request-URIs is only allowed for absoluteURIs)
*rename PARSE-HTTP-URL to URI-STRING->HTTP-URL
2005-04-04 15:35:50 +00:00
ba78eba433
*add comment on another mistake in RFC 2616 (query part of
...
Request-URIs only allowed for absoluteURIs)
*add copy of Appendix A of RFC 2396 for convenience
2005-04-04 13:36:54 +00:00
69948e9561
adapt definitions of interfaces and structures to new URI
...
parsing framework
2004-10-18 18:33:19 +00:00
ed1e4428c5
*move general procedures ESCAPE, UNESCAPE and their helper procs from
...
url.scm to uri.scm
-->Parser/Unparser for HTTP 1.1 URIs is now complete and resides in
url.scm; Encoder/Decoder applicable to URIs in general resides in uri.scm.
(All has been rewritten from scratch, next to nothing of Olin's code
is left).
<--
2004-10-18 18:23:03 +00:00
584bfa2cdb
*work around scsh bug (?) in definition of charset UNRESERVED
...
*new procs for encoding URIs:
-general proc ESCAPE taking an RegExp representing forbidden chars as argument
-specialized procs ESCAPE-SEGMENT, ESCAPE-QUERY
*new helper proc ASCII->ESCAPED
*use ESCAPE-SEGMENT and ESCAPE-URI in HTTP-URL->URI-STRING
2004-10-18 17:35:40 +00:00
c48446ba7f
*remove ESCAPE-URI (didn't reliably differentiate between different portions of
...
a URI)
*move INT->HEXCHAR to url.scm
2004-10-18 16:37:32 +00:00
44a8ef28be
*new procedure UNESCAPE (unescape URI-components using RegExps)
...
*move HEXCHAR->INT from uri.scm to here
*use UNESCAPE in PARSED-URI->HTTP-URL
2004-10-14 17:18:24 +00:00
9e71b351d4
*remove UNESCAPE-URI, HEX-DIGIT?
...
*move HEXCHAR->INT to url.scm
2004-10-14 17:14:44 +00:00
932f03a638
*fix two typos in RegExps
...
*better comments for PARSE-URI, SPLIT-PATH
*make SPLIT-PATH really accept PARSE-URI's return values
*restructure record-type HTTP-URL
*new procedure PARSED-URI->HTTP-URL
*rewrite PARSE-HTTP-URL to use PARSE-URI and PARSED-URI->HTTP-URL
*remove out-dated comments
*remove out-dated procedure PARSE-HTTP-URL-STRING
*remove DEFAULT-HTTP-SERVER (relict of server record-type)
*rewrite HTTP-URL->STRING
*rename HTTP-URL->STRING to HTTP-URL->URI-STRING
2004-10-11 17:01:32 +00:00
fe08e779f0
remove record-type server and associated procedures
...
(being a relict of parsing of general URIs)
2004-10-11 09:05:24 +00:00
41d3e29766
*add comment on how ambiguous definition of Request_URIs in RFC 2616
...
is 'solved' by uri-parser
*add comment on record-type server and associated procedures
2004-10-11 08:54:41 +00:00
8de8e01f0d
adapt documentation to reflect removal of old uri-parser and addition
...
of new one
2004-10-10 18:30:45 +00:00
a1e79c4fc7
parse HTTP 1.1 URIs:
...
* add RegExps
* add proc PARSE-URI
* add proc SPLIT-ABS-PATH
2004-10-06 19:10:49 +00:00
d9950a9b0b
remove PARSE-URI from exports of module uri
2004-10-06 19:08:19 +00:00
2cb8502f9e
remove uri-parser PARSE-URI
...
(completely out-of-date, has never seen RFC 2396)
2004-10-06 13:33:45 +00:00
649f374e8b
add comment on uri-parser
2004-10-06 13:29:06 +00:00
53e3e9672f
adapt to RFC terminology:
...
rename PARSE-HTTP-SERVERS-URL-FRAGMENT to PARSE-REQUEST-URI
rename variable uri-string to request-uri
2004-10-05 10:24:29 +00:00
cd22ab11d4
Corrected bug: SEVAL now generates a response-body even if the request's body isn't
...
form-url encoded or doesn't contain a program
2004-08-15 12:44:55 +00:00
38f2594ba5
emit less newlines
2004-08-15 12:40:06 +00:00
35565068fb
char-set:blank = LWS from RFC 2616 (after folding)
2004-08-15 12:02:36 +00:00
ffac0ebcac
simplified get-numeric-field-value (now uses string-trim-both),
...
adapted packages.scm
2004-08-15 11:49:15 +00:00
8bf71fc3a5
get-numeric-field-value: correct error message
2004-08-15 11:06:39 +00:00
44100cbf5e
Added type NO-BODY for responses which must not contain a message-body
...
(201, 304, 404). Added export of type-predicate no-body?. Adapted
SEND-HTTP-RESPONSE to check for no-body responses. Extended
MAKE-ERROR-RESPONSE to make responses 201, 304, 404.
2004-08-15 11:03:28 +00:00
0bb601a0e0
make server-generated webpages XHTML 1.0 Strict: emit prolog
...
(not tested)
2004-08-14 22:08:07 +00:00
549594bef4
with-tag* outputs no newlines
2004-08-14 22:05:06 +00:00
ef48e4e5ae
make-host-name-handler now uses get-header from sunet-utilities.scm
2004-08-14 22:03:19 +00:00
8cf841bad3
rename get-content-length to get-body-length-from-content-length
...
move get-body-length-from-content-length and get-numeric-field-value
from seval.scm to sunet-utilities.scm
adapt packages.scm
2004-08-14 21:58:11 +00:00
f8559581d2
GET-NUMERIC-FIELD-VALUE now uses GET-HEADER from utilities.scm
...
and returns #f if GET-HEADER does so
adapted GET-CONTENT-LENGHT
2004-08-14 21:18:12 +00:00
aea0e950ba
removed definition of GET-HEADER which conflicted with definition of
...
GET-HEADER in utilities.scm and wasn't exported anyway
2004-08-14 20:54:57 +00:00
ffbe3b21cd
factor out parsing of content-length header value -> GET-CONTENT-LENGTH
...
generalize parsing of content-length header value to parse all header field
values of the form 1*DIGIT -> GET-NUMERIC-FIELD-VALUE
check for valid content-length header in SEVAL before answering 200
TODO: SEVAL is still buggy for request with invalid _body_
2004-08-14 19:07:23 +00:00
9fcfcf36f0
add comments explaining why seval-handler is buggy
2004-08-14 15:47:29 +00:00
06ec0f0293
server-generated webpages -> XHTML 1.0 Strict:
...
add XML namespace declaration to html element
2004-08-13 15:49:19 +00:00
vibr