add comment on assumptions about entity in request to seval-handler
This commit is contained in:
		
							parent
							
								
									c9c45eae6e
								
							
						
					
					
						commit
						90fc61473e
					
				|  | @ -115,10 +115,15 @@ The request's body must be form-url encoded and contain a \"program=<sexp>\" pai | |||
| 
 | ||||
| ;;; Read an HTTP request entity body from stdin. The Content-length: | ||||
| ;;; entity-header field of request REQ tells how many bytes this entity | ||||
| ;;; is. The entity should be a URI-encoded form body. Pull out the | ||||
| ;;;     program=<stuff> | ||||
| ;;; string, extract <stuff>, uri-decode it, parse that into an s-expression, | ||||
| ;;; and return it. | ||||
| ;;; is.  | ||||
| 
 | ||||
| ;;; We assume, that the entity is "form-url encoded" data (see | ||||
| ;;; parse-forms.scm for a description of this encoding). This | ||||
| ;;; assumption is rather strange - it may safely be made only if | ||||
| ;;; there's a "Content-type: application/x-www-form-urlencoded" header. | ||||
| 
 | ||||
| ;;; Pull out the program=<stuff> string, extract <stuff>,  | ||||
| ;;; parse that into an s-expression, and return it. | ||||
| 
 | ||||
| (define (read-request-sexp bytes iport) | ||||
|   (let*  | ||||
|  |  | |||
		Loading…
	
		Reference in New Issue
	
	 vibr
						vibr