Skip to content

Conversation

@vendethiel
Copy link
Member

Not sure this is the best way to go about this, but...

@vendethiel
Copy link
Member Author

Travis says:

[IO::Socket::Async::SSL] # Cannot write to closed socket

@vendethiel
Copy link
Member Author

Not sure anymore.
image

my $routing-outcome = Cro::HTTP::LogTimeline::Route.log: $log-timeline-task, -> {
CATCH {
when X::Cro::Uri::ParseError {
emit Cro::HTTP::Response.new(:500status, :$request);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it should be 400 (Bad Request), since it's the client's fault.

@jnthn
Copy link
Member

jnthn commented Oct 6, 2020

The failure is this:

No such method 'raku' for invocant of type 'Str'

I wonder where we've ended up with that being called.

@jnthn
Copy link
Member

jnthn commented Oct 6, 2020

The problem being that 2019.03 is pre-rename, so has no .raku method. Of course, we could just bump to a newer version.

@vendethiel
Copy link
Member Author

I wonder where we've ended up with that being called.

No idea :).

FCO pushed a commit to FCO/cro-http that referenced this pull request Oct 1, 2025
FCO pushed a commit to FCO/cro-http that referenced this pull request Oct 1, 2025
@japhb
Copy link
Contributor

japhb commented Oct 1, 2025

Closing in favor of #209 which is a copy of this one

@japhb japhb closed this Oct 1, 2025
FCO pushed a commit to FCO/cro-http that referenced this pull request Oct 1, 2025
japhb added a commit that referenced this pull request Oct 2, 2025
Catch URI parse errors during routing (Copy from #114 vendethiel++)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants