Can't redirect to URLs ending with /

Bug #319140 reported by Marcel Zumstein, Oxinia GmbH on 2009-01-20
2
Affects Status Importance Assigned to Milestone
Squid
Incomplete
Undecided
Unassigned
eCAP
Undecided
Unassigned

Bug Description

When I use RequestLine::uri(const Area &aUri) to redirect my request, and the URL is the server root or some other URL ending with /, I get a 404. Everything works fine when I redirect to a regular URL or when I access a URL ending with / directly.

Tested with eCAP adapter 0.0.2 and Squid 3.1.0.3.

Alex Rousskov (rousskov) wrote :

How does this bug relate to bug #317451? That bug description says that using any relative URL results in a host application crash. Is this bug report specific to absolute URLs (the ones with a scheme and host name)?

Thank you,

Alex.

Changed in ecap:
assignee: nobody → rousskov

I tried it with absolute URLs. However, I now got the same bug even when I didn't change the URL with eCAP. The problem appears when I send a POST request. I suspect that either Apache can't handle POSTs to a directory properly, or they are illegal in http anyway.

Alex Rousskov (rousskov) wrote :

Where does 404 come from? Can you paste HTTP request headers sent from Squid to the origin server and HTTP response headers received by Squid from the origin server?

Alex Rousskov (rousskov) wrote :

Marking as incomplete until requested information (or Squid cache.log with full debugging enabled) is provided.

Changed in ecap:
status: New → Incomplete
Alex Rousskov (rousskov) on 2011-03-17
Changed in squid:
status: New → Incomplete
Alex Rousskov (rousskov) on 2011-03-17
Changed in ecap:
assignee: Alex Rousskov (rousskov) → nobody
Launchpad Janitor (janitor) wrote :

[Expired for eCAP because there has been no activity for 60 days.]

Changed in ecap:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers