Problem exporting csv of headers information on Windows

[Jamie Patrick-Burns]

Hello everyone, 

I am wondering if anyone has encountered a problem when exporting a csv of email headers in the Processing module. After navigating to the directory I wanted the file output and hitting the button, I received the following error: 

• HTTP Status 400 – Bad Request

  Type Exception Report

  Message Invalid character found in the request target [/epadd/export-headers?archiveID=1bd1034dd155e0a65266b39b9d06bf10e0f4f638c3b8cfdd73f8c148b9482408&exportType=csv&dir=C:\/Users/PatrickBurnsJ/ ]. The valid characters are defined in RFC 7230 and RFC 3986

I was able to export by typing in the path with encoded slashes: C:%5CUsers%5CPatrickBurnsJ%5C. It was interesting because I had no trouble with selecting file paths in previous steps of the Appraisal and Processing modules, rather than typing them in. I am curious if anyone else has encountered this? While there is a workaround solution, I may put in a GitHub issue to see if it can be fixed.

I've included the full error output below.

Thank you!

Jamie

HTTP Status 400 – Bad Request

Type Exception Report

 

Message Invalid character found in the request target [/epadd/export-headers?archiveID=1bd1034dd155e0a65266b39b9d06bf10e0f4f638c3b8cfdd73f8c148b9482408&exportType=csv&dir=C:\/Users/PatrickBurnsJ/ ]. The valid characters are defined in RFC 7230 and RFC 3986

 

Description The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

 

Exception

 

java.lang.IllegalArgumentException: Invalid character found in the request target [/epadd/export-headers?archiveID=1bd1034dd155e0a65266b39b9d06bf10e0f4f638c3b8cfdd73f8c148b9482408&exportType=csv&dir=C:\/Users/PatrickBurnsJ/ ]. The valid characters are defined in RFC 7230 and RFC 3986

                org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:494)

                org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:271)

                org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)

                org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890)

                org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1789)

                org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)

                org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)

                org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)

                org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

                java.base/java.lang.Thread.run(Thread.java:842)

Note The full stack trace of the root cause is available in the server logs.

 

Apache Tomcat/9.0.65

[Sally DeBauche]

Hi Jamie,

Thanks for reporting this issue. Jochen took a look and thinks that it is related to character encoding as the error suggested. He created a new version to test that you can download here:

epadd-standalon-11.1.2-alpha-fixed-header-export

Please download this file and run it from the command line like so (replacing the # with the amount of RAM that you want to allocate):

java -Xmx#g -jar .epadd-standalon-11.1.2-alpha-fixed-header-export.jar

Please give this a try and let us know how it goes.

Best Wishes,

Sally DeBauche

Digital Archivist

Stanford University Libraries

Pronouns:  she/her