404 on any request when not stadart port using

[Vovik1982]

When I using port 8080 my xcap-root seems like  http://xcapserver.domain.com:8080/xcap-root, but I have a client, who can use my server like  http://xcapserver.domain.com/xcap-root (without port - this client using the port in own connection settings). XCAP server returns 404 because xcap-root in the server's settings and in the request are not equal.

[Vovik1982]

It was wrong version. version 1.3.0

[adigeo]

As you already noticed yourself the client is broken and the server is right.

[Vovik1982]

I think you are wrong now.

In RFC2616 section 14.23 ( http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html) you can read: Host = "Host" ":" host [ ":" port ] ; Section 3.2.2 Section 3.2.2 ( http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.2.2) contains: http_URL = "http:" "" host [ ":" port ] [ abs_path [ "?" query ]]

As you can see, 'port' parameter is optional.

I think the client is right and XCAP server has the bug. I think, you are right and priority of this bug is minor, but it is bug.

[Vovik1982]

change priority again.

[adigeo]

I read your comment and I believe I understand your point. I beg to differ though but it could be just a point of view.

Port being optional does not mean it can be missing if you are using a a non-standard port. Missing, simply means that the port 80 is assumed for HTTP operations and 443 is used for HTTPS when they are not present. When using a custom port it must be properly indicated in the URL.

Secondly, even if your point would make sense because of the way you interpret it, will it work properly in a multi-domain platform where you could have multiple different roots and you could listen on multiple port numbers? You would need a complete fully qualified URL to determine each root correctly and this is not possible if you skip the port number.