Skip to content
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

bug: a detected url: "http://<html></html>" #72

Conversation

brbog
Copy link

@brbog brbog commented Jun 2, 2022

AllowSingleLevelDomain true together with IncludeBinaryContentInCrawling true causes an issue because of a detected url: "http://<html></html>"

More explanation + workaround is in the Javadoc of the tests.

I added JUnit5 dependencies because the "crawler4j-commons"-subproject was still virgin regarding testing. Maybe a good moment to decide whether continuing with Spock is useful or if it's time to gradually let go of him/it?

Bram Bogaert added 3 commits June 2, 2022 11:03
@rzo1
Copy link
Collaborator

rzo1 commented Jun 5, 2022

Hi! Thanks for the PR - I will look into it as soon as my ISP provides me with Internet again ;-)

@brbog
Copy link
Author

brbog commented Jun 7, 2022

See also issue #74

@rzo1
Copy link
Collaborator

rzo1 commented Jun 7, 2022

Maybe a good moment to decide whether continuing with Spock is useful or if it's time to gradually let go of him/it?

I don't speak spock, so I am +1 for dropping it ;)

@rzo1 rzo1 merged commit 4d2a769 into HHN:master Jun 7, 2022
@rzo1 rzo1 added the bug label Jun 7, 2022
@rzo1 rzo1 self-assigned this Jun 7, 2022
@rzo1 rzo1 added this to the v4.9.1 milestone Jun 7, 2022
@brbog brbog deleted the issue-AllowSingleLevelDomainTrue-and-IncludeBinaryContentInCrawlingTrue branch June 7, 2022 22:08
@brbog
Copy link
Author

brbog commented Jun 7, 2022

Maybe a good moment to decide whether continuing with Spock is useful or if it's time to gradually let go of him/it?

I don't speak spock, so I am +1 for dropping it ;)

I enjoyed the framework a lot and I actually can speak (and don't particularly like) Spock... I might regret this, but since there are not that many tests and all I need to get used to is WireMock (which is on my todo-list anyway), I'm volunteering to try to get rid of as much as possible of these tests -> read: translate to JUnit5 tests.

In my personal opinion I think Groovy was mostly a mistake for the Java community, and moving away from Spock after you moved away from Gradle is probably an evolution that you support? I have my "own ways" of course, but in the critical points I think we're not far apart, so just met me know if you feel like it would help :-).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants