-
Notifications
You must be signed in to change notification settings - Fork 40
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
RFC2910 & RFC8010 in 3.1.3 doesn't say something against attributes dublicates #133
Comments
RFC 2911 says that, not 2910. The problem is the citation. RFC 8011 (replaced RFC 2911) section 4.1.3 is where the citation lives:
|
Yep, but
Thats what i need:
|
Even the IPP reference implementation CUPS sometimes responds with duplicate attributes. So resilience for this issue is highly recommended. Adding the attribute again sounds okay to me. |
Agree.
Agree, i had to edit that lib and rebuild it to be able to use w/ cups correctly. |
Alternatively you could use this CupsClient which supports already some additional CUPS operations (e.g. job subscriptions and printer setup) |
No, this lib is fine. I made for me an IPP server using vert.x and this lib. |
So, how about contributing to the IPP community your IPP server? |
i need to make it nice and remove shitcode from :) thats for debug purposes. Works for win (spooler) & linux (cups), but i need to read more docs to make it nice and customisable. The advantage to use vertx it's cause it's small, fast, reactive & IPP use simple http/https. So vertx is a core and it have simple flow (which use kind of my "lib" which use that lib). |
Analyzed RFC8011 section 4.1.3 with above comments in consideration, we are reconsidering the logic. |
This is taken care and available in the latest release. Hence closing. |
Hi,
here is packet from debian11 cups, printing testing page just after adding the printer:
Here you say "RFC2910: Within an attribute group, if two or more attributes have the same name, the attribute group is malformed (see [RFC2911] section 3.1.3). Throw if someone attempts this."
jipp/jipp-core/src/main/java/com/hp/jipp/encoding/AttributeGroupImpl.kt
Line 19 in 7e2a5c0
While RFC2910 nor RFC8010 doesn't say that. It just mention how it should be formatted but doesn't say that having attribute dublicates aren't allowed.
So in actual case it's better to parse and add again a attribute dublicate into your hashset to overwrite existing value instead of throw an exception and interrupt the packet building flow (
ippStream.readPacket()
).The text was updated successfully, but these errors were encountered: