# Mutate\>Convert and URL Decode

**URL:** https://discuss.elastic.co/t/mutate-convert-and-url-decode/198745
**Category:** Logstash
**Created:** [September 9, 2019, 4:38pm UTC](https://discuss.elastic.co/t/mutate-convert-and-url-decode/198745 "2019-09-09T16:38:03Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![wwalker](https://avatars.discourse-cdn.com/v4/letter/w/43a26b/32.png) [@wwalker](https://discuss.elastic.co/u/wwalker)
#### Post date: [September 9, 2019, 4:38pm UTC](https://discuss.elastic.co/t/mutate-convert-and-url-decode/198745/1 "2019-09-09T16:38:03Z")

</div>

I am ingesting a document that is encoded as UTF-8BOM. This is causing an issue with the urldecode filter, though every other filter (json, mutate, translate, etc...) seems to process it just fine without changing the default selected charset.

I was wondering, could I resolve the issue by passing the field I want urldecode to look at to mutate's convert string function?

field to decode: url\_lookup

```auto
...
mutate {
  convert => {
    "url_lookup" => "string"
  }
}
urldecode {
  field => "url_lookup"
}
...

```

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 7, 2019, 4:38pm UTC](https://discuss.elastic.co/t/mutate-convert-and-url-decode/198745/2 "2019-10-07T16:38:09Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.