You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,9 +110,9 @@ Flow-wise, Clammit is straightforward. It sets up an HTTP server to accept
110
110
incoming requests (main.go):
111
111
112
112
1. Each request is passed to the forwarder (forwarder/forwarder.go)
113
-
2. The forwarder dowloads the request body (as it will be used at least twice)
113
+
2. The forwarder downloads the request body (as it will be used at least twice)
114
114
3. The forwarder passes the request to the clam interceptor (clam\_interceptor.go)
115
-
4. The only request that will be tested will have methods POST/PUT/PATCH and content-type "multipart/form-data"
115
+
4. The only request that will be tested will have methods POST/PUT/PATCH
116
116
5. The clam interceptor locates and sends each form-data field to ClamD
117
117
6. For any positive response, the interceptor will write an HTTP response and return (and the forwarder will not attempt to forward the request)
118
118
7. If the interceptor OKs the request, the forwarder constructs a new HTTP request and forwards to the application
@@ -170,9 +170,8 @@ This method will return JSON giving the current status of Clammit and its connec
170
170
POST /clammit/scan
171
171
```
172
172
173
-
This is the endpoint to submit files for scanning only. The request must have content-type ```multipart/form-data```
174
-
and any files to be scanned should be attached as file objects. Clammit will return an HTTP status code of 200 if
175
-
the request is clean and 418 if there is a bad attachment.
173
+
This is the endpoint to submit files for scanning only. Any files to be scanned should be attached as file objects.
174
+
Clammit will return an HTTP status code of 200 if the request is clean and 418 if there is a bad attachment.
176
175
177
176
### Test
178
177
@@ -181,7 +180,7 @@ the request is clean and 418 if there is a bad attachment.
181
180
```
182
181
183
182
This will return a simple file upload page, to test sending requests to Clammit. These pages are located in the
184
-
testing/ subdirectory.
183
+
testing/ sub-directory.
185
184
186
185
## Resources
187
186
@@ -197,7 +196,7 @@ Run ```make test```
197
196
* It does not attempt to recursively scan fields - e.g. attachments in an email chain
198
197
* It does not try to be particularly clever with storing the body, which means that a DOS attack by hitting it simultaneously with a gazillion small files is quite possible.
0 commit comments