Thanks, Jay. It is definitely POST, and there is a Content-Length header,
so it seems like the problem is indeed #3. I was expecting the raw data to
be there even if it had been parsed — I believe the POST data of #
"corpus=austen&tool=corpus.CorpusMetadata" was also parsed into bindings
(though no
Hi Philip,
I don't necessarily know the answer and it's possible that it is an
error. I'll explain what it is doing and maybe that will help us move
forward.
1) The request-bindings/raw is just an abstraction over
request-post-data/raw (and the URI)
2) The request-post-data/raw is always #f for G
Thanks for your comments.
The only legal files to upload in this case are plain text, so I'm not too
worried about size. I'm relying on the web-server libraries to deal with
any malicious attempts to send overwhelmingly large files (if that's a bad
idea, I'd definitely appreciate hearing it!). Oth
I don't know the answer to your particular questions with `web-server`
(I've made my own implementations of this in the past), and these
comments might not apply to your particular application, but I'll
mention here for whomever is interested...
It sounds like you're using this, which might pr
I'm working on a Racket web application for which I need to proxy certain
requests to a non-Racket service over HTTP. I've built a very basic proxy
on top of http-sendrecv/url that works quite well for the most part.
For POST requests, I pass the request-post-data/raw of the original request
as th
5 matches
Mail list logo