# SPARQL LOAD: Stardog should not guess format from URI

**URL:** <https://community.stardog.com/t/sparql-load-stardog-should-not-guess-format-from-uri/218>\
**Category:** Bug\
**Created:** [April 5, 2017, 8:35am UTC](https://community.stardog.com/t/sparql-load-stardog-should-not-guess-format-from-uri/218 "2017-04-05T08:35:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![retog](https://avatars.discourse-cdn.com/v4/letter/r/e0b2c6/32.png) [@retog](https://community.stardog.com/u/retog)\
**Post date:** [April 5, 2017, 8:35am UTC](https://community.stardog.com/t/sparql-load-stardog-should-not-guess-format-from-uri/218/1 "2017-04-05T08:35:51Z")

</div>

Currently on a SPARQL LOAD query Stardog sends a request to the server serving the graph to be loaded with

```
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2

```

This doesn’t seem very appropriate as an RDF representation should be preferred.

But what’s worse is that Stardog ignores the Content-Type header in the response but instead guesses the response type from how the IRI of the loaded resource ends. This is wrong as URIs are opaque.

---

<div class="post-metadata">

**Author:** ![stephen](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/stephen/32/27_2.png) [@stephen](https://community.stardog.com/u/stephen)\
**Post date:** [April 5, 2017, 3:03pm UTC](https://community.stardog.com/t/sparql-load-stardog-should-not-guess-format-from-uri/218/2 "2017-04-05T15:03:38Z")

</div>

Hi,

You’re absolutely right and I have opened an internal ticket for us to address both the Accept header of the request and use of the Content-Type header of the response during the 5.x release cycle.

Thanks for the report!