-
Notifications
You must be signed in to change notification settings - Fork 760
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP response only results in garbage bytes #206
Comments
You need to go to |
We need to improve the docs because 3.2 is buggy. See https://github.com/internetarchive/heritrix3/wiki#latest-releases and https://trello.com/c/Inb8MW5w/29-establish-offical-heritrix-releases |
@anjackson Thanks Andy. Turns out the docs actually mention this but I had overlooked it. Works now! I'll close this issue now. |
it seems that 3.3 does not allow http access? is there a way to enforce http (not https) so that we can use heritrix behind proxy? |
I just ran into this same problem. A HTTP to HTTPS redirect, or a note in the docs saying you must access the web UI over HTTPS would be appreciated. |
I'm trying to run the latest Heritrix build (build heritrix-3.3.0-20180529.100446-105-dist.tar.gz which I downloaded here) for some tests.
I try to start Heritrix with the below command::
This works, but when I open http://localhost:8443/ in my browser (Firefox), it only shows 6 garbled characters (Chromium returns a ERR_INVALID_HTTP_RESPONSE error). Saving the page and opening it in a Hex editor shows these 7 bytes:
Some info on Java on my system:
Here's the Heritrix log file:
The log contains a number of warnings, but I have no idea if they are related to this.
Perhaps I'm doing something wrong myself (this my first attempt at installing and running Heritrix). Anyway, if anyone could give me a hint on how to make this work that would be really helpful. (Side note: I initially tried the "stable" 3.2 release, but gave up on that because of the dependency on Java 7.)
The text was updated successfully, but these errors were encountered: