We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When the "output=xml" parameter is added to the query string the response is a raw Solr json with the content-type: text/xml .
Open one of these examples on any browser:
Example 1 Example 2
Last time I checked the XML API I got a valid XML response.
I am not sure but I think it might be related to the XSLT file changes made for the new Solr version.
Old solr: https://github.com/scieloorg/search-journals/blob/master/solr/5.5.5/cores/articles/xslt/export-xml.xsl#L50
New solr: https://github.com/scieloorg/search-journals/blob/master/solr/8.5.1/cores/solrdata/data/articles/xslt/export-xml.xsl#L49
The text was updated successfully, but these errors were encountered:
Em conversa com a equipe esse endpoint será removido, já que essa ferramenta não tem esse proposito.
Sorry, something went wrong.
gitnnolabs
No branches or pull requests
Descrição do problema
When the "output=xml" parameter is added to the query string the response is a raw Solr json with the content-type: text/xml .
Passos para reproduzir o problema
Open one of these examples on any browser:
Example 1
Example 2
Comportamento esperado
Last time I checked the XML API I got a valid XML response.
Screenshots ou vídeos
Anexos
I am not sure but I think it might be related to the XSLT file changes made for the new Solr version.
Old solr: https://github.com/scieloorg/search-journals/blob/master/solr/5.5.5/cores/articles/xslt/export-xml.xsl#L50
New solr: https://github.com/scieloorg/search-journals/blob/master/solr/8.5.1/cores/solrdata/data/articles/xslt/export-xml.xsl#L49
Ambiente utilizado
The text was updated successfully, but these errors were encountered: