caching is controlled by your server’s headers. I suggest that while you’re 
debugging, you should open your browser’s developer console and “disable 
caching”.  Then you can rule that out.

> On Aug 10, 2016, at 4:14 PM, Andrew Campbell 
> <[email protected]> wrote:
> 
> I am having real trouble with my accept headers. 
> 
> I have two Swagger files. The only difference is one has 
> 
> "host": "example.com"
> 
> And the other has 
> 
> "host": "my.actual.domain"
> 
> When I use the example.com version, the value of the accept header is set 
> correctly.
> 
> When I use the version with my actual domain, the accept header is always set 
> to text/plain.
> 
> What is causing this? Earlier today, I was making changes to the version with 
> my actual domain, and the accept header was being set to text/plain. Could 
> there be caching of some sort going on somewhere? I ahve been having other 
> issues with caching, as described here: 
> https://groups.google.com/forum/#!topic/swagger-swaggersocket/ate3lFQz7eg
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Swagger" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
You received this message because you are subscribed to the Google Groups 
"Swagger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to