-
Notifications
You must be signed in to change notification settings - Fork 3
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
Change content type to "UTF-8" #81
Comments
The adding of the «charset=utf-8» in the content header will not be any breaking change. bLink system will not validate if the enconding complies with UTF-8 therefore there will be no impact on serivce user nor service provider. |
Meeting Notes 4.4.24The pull request will be prepared and discussed on next meeting. |
Meetin Notes 20.6.24This issue will be discussed on 15th August. |
Meeting Notes 15.8.24The pull request has to be generated and presented on 26th September by @RaulGuirao. |
IS:
application/xml
.<?xml version="1.0" encoding="UTF-8"?>
is declared inside the file as text, but not mandatory.... so the content-type negotiation would be up to the SU / SP ...
PROPOSAL
application/xml
toapplication/xml; charset=utf-8
in Release 5.0 and never talk about the issue again :-).Here the location in the specification:
One of the sections affected - PAIN.001 upoad in PSS:
The text was updated successfully, but these errors were encountered: