# Urldecode plugin for ingest node? **URL:** \ **Category:** Elasticsearch\ **Created:** [September 21, 2016, 6:37am UTC](https://discuss.elastic.co/t/urldecode-plugin-for-ingest-node/61080 "2016-09-21T06:37:34Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![obudiman](https://avatars.discourse-cdn.com/v4/letter/o/e19adc/32.png) [@obudiman](https://discuss.elastic.co/u/obudiman)\ **Post date:** [September 21, 2016, 6:37am UTC](https://discuss.elastic.co/t/urldecode-plugin-for-ingest-node/61080/1 "2016-09-21T06:37:34Z")
Just wondering if there is a plan to bring this or any other workaround to have the same result? We are in need to parse the apache log and user don't really like the encoded URL string on the output. We can do it easily in logstash with urldecode, so just hoping there's a way to do this with ingest node. ---
**Author:** ![talevy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/talevy/32/44896_2.png) [@talevy](https://discuss.elastic.co/u/talevy)\ **Post date:** [September 27, 2016, 2:26am UTC](https://discuss.elastic.co/t/urldecode-plugin-for-ingest-node/61080/2 "2016-09-27T02:26:57Z")
Probably not for 5.0 release, might be a potential candidate for a new processor later on if it makes sense. Right now, a workaround can be implemented in the GsubProcessor with a regex replacement that matches the url escaped characters ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:17pm UTC](https://discuss.elastic.co/t/urldecode-plugin-for-ingest-node/61080/3 "2017-07-05T22:17:05Z")