I guess this just parses it, but doesn't serialize the data to the db. Changing this to a draft for now.

@ato would adding method to the db require a new indexVersion (5)?

Yeah. New fields requires a new version number so that the reading code knows what to expect. The approach I was thinking about was to add an extra serialized field that stores a blob of json with all the extra fields (since as far as I know they could be arbitrarily complex json structures).

you also have to add a requestBody field, no?

java.lang.IllegalArgumentException: no such capture field: requestBody
at outbackcdx.Capture.put(Capture.java:554)
at outbackcdx.Capture.fromCdxjLine(Capture.java:437)
at outbackcdx.Capture.fromCdxLine(Capture.java:388)
at outbackcdx.Webapp.post(Webapp.java:249)
at outbackcdx.Webapp.lambda$new$3(Webapp.java:102)
at outbackcdx.Web$Route.handle(Web.java:312)
at outbackcdx.Web$Router.handle(Web.java:236)
at outbackcdx.Webapp.handle(Webapp.java:594)
at outbackcdx.Web$Server.serve(Web.java:50)
at outbackcdx.NanoHTTPD$HTTPSession.execute(NanoHTTPD.java:848)
at outbackcdx.NanoHTTPD$1$1.run(NanoHTTPD.java:207)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)

I'm going to close this since we now support arbitrary CDXJ fields (commit 9d73df3) which I think should cover this. Feel free to reopen if I'm wrong though!